Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When running hammer content-host list with the --by option to sort by INSTALLABLE ERRATA it doesn't.
Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-0.5.1.11-4.el7sat.noarch
How reproducible:
Always
Steps to Reproduce:
On satellite 6.2 try to list content-host with --by option tp sort by 'INSTALLABLE ERRATA'.
# hammer -u admin -p password content-host list --organization-id <id> --content-view <content-view-name. --lifecycle-environment <lifecycle environment name> --by 'INSTALLABLE ERRATA'
Actual results:
Do not sort list as per installable errata.
For ex:
-------------------------------------|---------------|-------------------
ID | NAME | INSTALLABLE ERRATA
-------------------------------------|---------------|-------------------
6f0373b3-05b1-47dd-b3bf-xxxxxxxxxxxx | system01 | 0
8b8b8ff7-2d01-444b-97ae-xxxxxxxxxxxx | system02 | 6
a398c2a6-514c-4904-a737-xxxxxxxxxxxx | system03 | 0
c511e4e7-63a8-4f8b-b667-xxxxxxxxxxxx | system04 | 30
Expected results:
Should list content-hosts as per installable errata.
For ex:
-------------------------------------|---------------|-------------------
ID | NAME | INSTALLABLE ERRATA
-------------------------------------|---------------|-------------------
c511e4e7-63a8-4f8b-b667-xxxxxxxxxxxx | system04 | 30
8b8b8ff7-2d01-444b-97ae-xxxxxxxxxxxx | system02 | 6
6f0373b3-05b1-47dd-b3bf-xxxxxxxxxxxx | system01 | 0
a398c2a6-514c-4904-a737-xxxxxxxxxxxx | system03 | 0
Additional info:
In 6.3.0, the `--by` option is removed and replaced with the `--order` option. The query above would be changed like so:
```
# Before
hammer -u admin -p password content-host list --organization-id <id> --content-view <content-view-name> --lifecycle-environment <lifecycle environment name> --by 'INSTALLABLE ERRATA'
# After
hammer -u admin -p password content-host list --organization-id <id> --content-view <content-view-name> --lifecycle-environment <lifecycle environment name> --order 'installable_errata [desc]'
```
Verified.
Version Tested: Satellite-6.3 Snap 10.
CLI output screen-shots attached.
** RPM package versions:
satellite-6.3.0-16.0.beta.el7sat.noarch
foreman-1.15.2-1.el7sat.noarch
katello-3.4.4-2.el7sat.noarch
tfm-rubygem-hammer_cli-0.10.2-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman-0.10.2-1.el7sat.noarch
As the content host resource is no longer there, host will be used instead on sat 6.3.
Subcommand 'content-host' is also not present in hammer so this issue will not exist on 6.3.
** Note that - in 6.3.0, `--by` option is replaced by `--order` option.
For example -
hammer -u admin -p password host list --order 'name desc'
Comment 5Satellite Program
2018-02-21 16:49:54 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
For information on the advisory, and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:0336