Bug 1405992

Summary: All settings of a host's hostgroup are not getting update with hammer
Product: Red Hat Satellite Reporter: vijsingh
Component: HammerAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Ondřej Pražák <oprazak>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1.10CC: bbuckingham, bfruehling, dhlavacd, dlobatog, jcallaha, lzap, mhulan, oprazak, tstrachota, vijsingh
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: http://projects.theforeman.org/issues/13775
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 17:01:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description vijsingh 2016-12-19 12:53:05 UTC 
Description of problem:

All settings of a host's hostgroup are not getting update with hammer

i.e. lifecycle Environment , Content View , Puppet Environment , Content Source.


Version-Release number of selected component (if applicable):

Satellite - 6.1.11
Hammer cli - rubygem-hammer_cli-0.1.4.13-1.el7sat.noarch


How reproducible:
Each time.


Steps to Reproduce:

1. Create a hostgroup with 'lifecycle Environment , Content View , Puppet Environment , Content Source' 

2. Run the below hammer command to update host ..

  # hammer host update --id HOSTID --hostgroup HOSTGROUPNAME

3. Check the applied setting ( lifecycle Environment , Content View , Puppet Environment , Content Source ) with WEB GUI for host.

Actual results:

lifecycle Environment , Content View , Puppet Environment , Content Source will not be update.

Expected results:

lifecycle Environment , Content View , Puppet Environment , Content Source should be update while updating the host with hostgroup.

Additional info:
Comment 2 Tomas Strachota 2016-12-21 14:53:29 UTC 
Unfortunately I wasn't able to reproduce neither in 6.1.10 nor 6.2.

Can you please provide full debug logs of:
 hammer -d host info --id XY
 hammer -d host update --id XY --hostgroup THE_HOSTGROUP
 hammer -d host info --id XY
Comment 4 vijsingh 2016-12-21 17:02:39 UTC 
hammer debug logs has been attached .

also Red Hat satellite version is 6.1.11
Comment 6 Daniel Lobato Garcia 2017-01-03 09:17:45 UTC 
I have a suspicion this behavior is fixed by http://projects.theforeman.org/issues/13775 - so I'll link the issues. We had a similar problem upstream with that.

Let us know if that fixes the problem. I'll propose the change for 6.2.
Comment 7 Daniel Lobato Garcia 2017-01-03 09:19:42 UTC 
Connecting redmine issue http://projects.theforeman.org/issues/13775 from this bug
Comment 11 Ondřej Pražák 2017-08-09 12:48:56 UTC 
Verified.

Sat-6.3.0 snap 10
Comment 12 Bryan Kearney 2018-02-21 17:01:16 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