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.