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:
Changing a host parameter using "hammer host update" removes the existing Puppet classes assigned to the host.
Version-Release number of selected component (if applicable):
6.5 and 6.6.2
How reproducible:
Always
Steps to Reproduce:
1. Display existing Puppet classes on a host
[root@satellite ~]# hammer host puppet-classes --host rhel77-core.lab-internal.localdomain
---|-----------------------
ID | NAME
---|-----------------------
1 | access_insights_client
---|-----------------------
2. Update a parameter of the host, here the owner
[root@satellite ~]# hammer host update --name rhel77-core.lab-internal.localdomain --owner user1
Host updated.
3. Check existing Puppet classes on a host
[root@satellite ~]# hammer host puppet-classes --host rhel77-core.lab-internal.localdomain
---|-----
ID | NAME
---|-----
Actual results:
All assigned Puppet classes are removed
Expected results:
All existing/assigned Puppet class to the host should remain if any update is done to the host using "hammer host update"
Additional info:
HOTFIX is available for Satellite 6.6
INSTRUCTIONS:
1. take a backup of Satellite server
2. download the attached hotfix RPM and copy it to Satellite server
3. # yum install ./tfm-rubygem-hammer_cli_foreman-0.17.0.8-2.HOTFIXRHBZ1809952.el7sat.noarch.rpm --disableplugin=foreman-protector
Since this hotfix is for hammer, no service restart is required
After the hotfix is installed, a host can be updated with `hammer host update` and the assigned puppet classes will be retained
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 (Satellite 6.8 Satellite Tools 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/RHBA-2020:4367