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.
DescriptionOndrej Gajdusek
2020-08-06 07:42:33 UTC
Description of problem:
There is no way to resolve traces for a particular host using Hammer CLI. There is an API endpoint for it, but Hammer does not use it.
/katello/api/traces/resolve
Version-Release number of selected component (if applicable):
6.8
tfm-rubygem-hammer_cli_katello-0.22.2-1.el7sat.noarch
tfm-rubygem-katello-3.16.0-0.15.rc4.1.el7sat.noarch
How reproducible:
always
Actual results:
Hammer does not provide the "resolve" host traces functionality.
Expected results:
Hammer should provide user with the possibility to remediate/resolve traces on hosts.
Additional info:
As of now, there is only the "list" functionality.
# hammer host traces --help
Usage:
hammer host traces [OPTIONS] SUBCOMMAND [ARG] ...
Parameters:
SUBCOMMAND Subcommand
[ARG] ... Subcommand arguments
Subcommands:
list List services that need restarting on the host
Options:
-h, --help Print help
Verified - tfm-rubygem-hammer_cli_katello-0.22.2.2-1.el7sat.noarch, tfm-rubygem-katello-3.16.0.10-1.el7sat.noarch
I verified also the other functionality that the Katello PR brought in.
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 (Important: Satellite 6.8 release), 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-2020:4366
Description of problem: There is no way to resolve traces for a particular host using Hammer CLI. There is an API endpoint for it, but Hammer does not use it. /katello/api/traces/resolve Version-Release number of selected component (if applicable): 6.8 tfm-rubygem-hammer_cli_katello-0.22.2-1.el7sat.noarch tfm-rubygem-katello-3.16.0-0.15.rc4.1.el7sat.noarch How reproducible: always Actual results: Hammer does not provide the "resolve" host traces functionality. Expected results: Hammer should provide user with the possibility to remediate/resolve traces on hosts. Additional info: As of now, there is only the "list" functionality. # hammer host traces --help Usage: hammer host traces [OPTIONS] SUBCOMMAND [ARG] ... Parameters: SUBCOMMAND Subcommand [ARG] ... Subcommand arguments Subcommands: list List services that need restarting on the host Options: -h, --help Print help