Actions
Bug #25145
closedHammer command with content view version --order is not working as expected.
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1624416
Description of problem:
After upgrading Satellite 6.2 to 6.3 hammer content view version --order parameter not functioning as expected.
Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-0.11.0.1-1.el7sat.noarch
How reproducible:
Steps to Reproduce:
1. Publish multiple version of a content view.
2. Run # hammer --output csv content-view version list --content-view client --organization redhat --order 'version DESC'
Actual results:
- hammer --output csv content-view version list --content-view client --organization redhat --order 'version DESC'
ID,Name,Version,Lifecycle Environments
Expected results:
- hammer --output csv content-view version list --content-view client --organization redhat --order 'version DESC'
ID,Name,Version,Lifecycle Environments
4,client 2.0,2.0,Library
3,client 1.0,1.0,"Dev, Prod"
Additional info:
This parameter is working well in Satellite 6.2.
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Stephen Benjamin
- Pull request https://github.com/Katello/katello/pull/7741 added
Updated by Justin Sherrill over 6 years ago
- Subject changed from Hammer command with content view version --order is not working as expected. to Hammer command with content view version --order is not working as expected.
- Target version set to Katello 3.9.0
- Triaged changed from No to Yes
- Fixed in Releases Katello 3.9.0 added
Updated by Stephen Benjamin over 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|4d473adaea7d100a73226a61bd44de8e751a63b2.
Actions