Description of problem: Updating the content view, activation-key and puppet environment of a hostgroup will not update these settings in the existing hosts that are assigned to the hostgroup. This is a conflicting behavior with the parameters and puppet modules that are always inherited by the host from the hostgroup. Proposal is to have an explicit setting at host level that it will always inherit the content view, activation-key and puppet environment from the hostgroup. Without this feature it is complex and error prone (because it requires multiple manual actions) to update the content views / puppet environments of hosts per hostgroup. Especially with nested hostgroups. Where you want to change the default on the top hostgroup and expect it to be applied on all hosts. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create hostgroups: production/group1/subgroup1 production/group1/subgroup2 production/group2/subgroup1 production/group2/subgroup2 2. Create one or more hosts in each subgroup 3. Change the content view on hostgroup production Actual results: Content view is not changed on the hosts Expected results: Content view is changed also on all hosts Additional info: This is also a regression compared to Cobbler that had this inheritance.
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
*** This bug has been marked as a duplicate of bug 1265629 ***