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:
Updating content-view for a host using hammer removes host's parameters
Version-Release number of selected component (if applicable):
tfm-rubygem-hammer_cli-0.11.0.1-1.el7sat.noarch
How reproducible:
Always
Steps to Reproduce:
1. #hammer host info --name host.example.com
...
Parameters:
kt_activation_keys => test_key
tag.purpose => testing
All parameters:
kt_activation_keys => test_key
tag.purpose => testing
...
2. #hammer host update --name host.example.com --content-view content_view_2
3. #hammer host info --name host.example.com
...
Parameters:
All parameters:
...
Actual results:
Custom parameters gets removed/wiped out
Expected results:
Custom parameters should be retained
Additional info:
1. Customer is creating this parameter manually kt_activation_keys might be because in documentation it is not so clear.
2. Same task can be done through web UI with those custom parameters 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, 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:2927
Description of problem: Updating content-view for a host using hammer removes host's parameters Version-Release number of selected component (if applicable): tfm-rubygem-hammer_cli-0.11.0.1-1.el7sat.noarch How reproducible: Always Steps to Reproduce: 1. #hammer host info --name host.example.com ... Parameters: kt_activation_keys => test_key tag.purpose => testing All parameters: kt_activation_keys => test_key tag.purpose => testing ... 2. #hammer host update --name host.example.com --content-view content_view_2 3. #hammer host info --name host.example.com ... Parameters: All parameters: ... Actual results: Custom parameters gets removed/wiped out Expected results: Custom parameters should be retained Additional info: 1. Customer is creating this parameter manually kt_activation_keys might be because in documentation it is not so clear. 2. Same task can be done through web UI with those custom parameters retained.