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:
Configuration is lost when updating hostgroup with hammer
When used "hammer hostgroup update" to change a certain value, some other configurations about the host is lost.
For example:
A host group with following puppet settings:
# hammer hostgroup info --name rhel7-snp-client-lab | grep -A1 Puppet
Puppet CA Proxy Id: 2
Puppet Master Proxy Id: 2
ComputeProfile:
Puppetclasses:
cis::el7all
If updated the Puppetclasses parameter, it will loose the information about puppet proxy:
# hammer hostgroup update --name rhel7-snp-client-lab --puppet-classes 'cis::el7all'
Hostgroup updated
# hammer hostgroup info --name rhel7-snp-client-lab | grep -A1 Puppet
Puppet CA Proxy Id:
Puppet Master Proxy Id:
ComputeProfile:
Puppetclasses:
cis::el7all
And vise versa.
I would expect updating a single parameter shouldn't affect other parameters. Unless there is any dependences, which should be clearly documented.
Version-Release number of selected component (if applicable): Satellite 6.1
How reproducible: Always
Expected results:
Updating a single parameter shouldn't affect other parameters. Unless there is any dependences, which should be clearly documented.
Comment 16Satellite 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
Description of problem: Configuration is lost when updating hostgroup with hammer When used "hammer hostgroup update" to change a certain value, some other configurations about the host is lost. For example: A host group with following puppet settings: # hammer hostgroup info --name rhel7-snp-client-lab | grep -A1 Puppet Puppet CA Proxy Id: 2 Puppet Master Proxy Id: 2 ComputeProfile: Puppetclasses: cis::el7all If updated the Puppetclasses parameter, it will loose the information about puppet proxy: # hammer hostgroup update --name rhel7-snp-client-lab --puppet-classes 'cis::el7all' Hostgroup updated # hammer hostgroup info --name rhel7-snp-client-lab | grep -A1 Puppet Puppet CA Proxy Id: Puppet Master Proxy Id: ComputeProfile: Puppetclasses: cis::el7all And vise versa. I would expect updating a single parameter shouldn't affect other parameters. Unless there is any dependences, which should be clearly documented. Version-Release number of selected component (if applicable): Satellite 6.1 How reproducible: Always Expected results: Updating a single parameter shouldn't affect other parameters. Unless there is any dependences, which should be clearly documented.