This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 1984107 - Hammer output message is inconsistent across sub-commands after the entity update
Summary: Hammer output message is inconsistent across sub-commands after the entity up...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-20 17:23 UTC by Ondrej Gajdusek
Modified: 2024-06-06 01:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 01:01:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 33130 0 Normal New Hammer output message is inconsistent across sub-commands after the entity update 2021-07-23 17:10:30 UTC
Red Hat Issue Tracker   SAT-20874 0 None Migrated None 2024-06-06 01:01:47 UTC

Description Ondrej Gajdusek 2021-07-20 17:23:34 UTC 
Description of problem:
BZ1868310 introduced a new type of message after the entity is updated and when the user provides no extra arguments.
New message: "Nothing to update".
Old message: "<entity_type> updated."
However, this message is not shown for some Hammer sub-commands and the former message "<entity_type> updated." is printed out. This makes the output messages inconsistent across the sub-commands.
Affected sub-commands are listed in the reproducer below.

Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli_foreman_remote_execution-0.2.1-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.3.0-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_discovery-1.0.2-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_templates-0.2.0-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_azure_rm-0.2.1-1.el7sat.noarch
tfm-rubygem-hammer_cli-2.5.1-1.el7sat.noarch
tfm-rubygem-hammer_cli_katello-1.1.2-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_admin-0.0.10-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_virt_who_configure-0.0.8-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.15-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_ansible-0.3.3-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman-2.5.1-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_openscap-0.1.12-2.el7sat.noarch


How reproducible:
Every time

Steps to Reproduce (hammer sub-command and the actual command that produces the output):
activation-key: hammer activation-key update --organization-id 1 --id 1
ansible (possibly, but I was unable to test it due to BZ1983760)
content-credentials: hammer content-credentials update --id 1
domain: hammer domain update --id 1
filter: hammer filter update --id 336
host: hammer host update --id 1
host-collection: hammer host-collection update --id 1
job-template: hammer job-template update --id 174
virt-who-config: hammer virt-who-config update --id 1

Actual results:
Activation key updated.
Content Credential updated.
Domain [my.vms.redhat.com] updated.
Permission filter for [Config group] updated.
Host updated.
Host collection updated.
Job template updated
Virt Who configuration [myconfig] updated

Expected results:
"Nothing to update" message in all cases.

Additional info:
Sub-commands that are not listed in the reproducer section, produce a "Nothing to update" message or explicitly require additional arguments to be provided by the user.
Comment 1 Oleh Fedorenko 2021-07-23 17:09:41 UTC 
Thank you a lot for exact commands that need revisiting! It's worth mentioning though that it seems like this issue comes from a few plugins that should be fixed, thus this will require more than one package to release or a few cherry-picks for different components at once.
Comment 2 Oleh Fedorenko 2021-07-23 17:10:29 UTC 
Created redmine issue https://projects.theforeman.org/issues/33130 from this bug
Comment 3 Bryan Kearney 2021-12-18 20:05:10 UTC 
Upstream bug assigned to aabramov
Comment 4 Bryan Kearney 2021-12-18 20:05:12 UTC 
Upstream bug assigned to aabramov
Comment 7 Eric Helms 2024-06-06 01:01:48 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.