Bug 1570489
Summary: | [Satellite 6] - hammer by / order option not working for sorting content-view versions | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | jalviso <jalviso> |
Component: | Content Views | Assignee: | Rahul Bajaj <rabajaj> |
Status: | CLOSED WONTFIX | QA Contact: | Lai <ltran> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.1 | CC: | apatel, arahaman, bkearney, dhlavacd, kgaikwad, rabajaj |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-03 12:53:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
jalviso
2018-04-23 04:50:21 UTC
Hello, I would like to share some more details on the same issue with three scenarios performed on Satellite 6.3 as below: A) Listing specific content view using option "--content-view=": # hammer content-view version list --content-view=installation-kickstart --organization-id=1 ---|----------------------------|---------|----------------------- ID | NAME | VERSION | LIFECYCLE ENVIRONMENTS ---|----------------------------|---------|----------------------- 3 | installation-kickstart 2.0 | 2.0 | Library 2 | installation-kickstart 1.0 | 1.0 | ---|----------------------------|---------|----------------------- # hammer content-view version list --content-view=installation-kickstart --organization-id=1 --order=version ---|------|---------|----------------------- ID | NAME | VERSION | LIFECYCLE ENVIRONMENTS ---|------|---------|----------------------- While using "--order=version" it does not list the output at all. B) Listing all content views: # hammer content-view version list --organization-id=1 ---|-------------------------------|---------|----------------------- ID | NAME | VERSION | LIFECYCLE ENVIRONMENTS ---|-------------------------------|---------|----------------------- 3 | installation-kickstart 2.0 | 2.0 | Library 6 | ccv 1.0 | 1.0 | Library 5 | reproduce 1.0 | 1.0 | Library 4 | Test 1.0 | 1.0 | Library, Production 2 | installation-kickstart 1.0 | 1.0 | 1 | Default Organization View 1.0 | 1.0 | Library ---|-------------------------------|---------|----------------------- # hammer content-view version list --organization-id=1 --order=version ---|------|---------|----------------------- ID | NAME | VERSION | LIFECYCLE ENVIRONMENTS ---|------|---------|----------------------- While using "--order=version" it does not list the output at all. C) --order 'name DESC' or 'name ASC'(sorting based on name): # hammer content-view version list --organization-id=1 --order 'name DESC' ---|------|---------|----------------------- ID | NAME | VERSION | LIFECYCLE ENVIRONMENTS ---|------|---------|----------------------- While using "--order=version" it does not list the output at all. --order parameter does not work in either of the above three scenarios whereas scenario A) and B) works as expected in Satellite 6.2.14 The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you. Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you. |