Description of problem: When editing a hostgroup, if the 'Environment' or 'Content View' select boxes are changed on the 'Host Group' tab, all puppet module allocations under the 'Puppet Classes' tab are immediately cleared. Version-Release number of selected component (if applicable): 6.0.4 How reproducible: Always Steps to Reproduce: 1.Edit a host group 2. Go to the 'Puppet Classes' tab and ensure it has puppet modules assigned 3. Go to the 'Host Group' tab and change either the 'Lifecycle Environment' or the 'Puppet Environment/Content View' tab 4. Go back to the 'Puppet Classes' tab Actual results: All puppet modules have been cleared from the hostgroup Expected results: All puppet modules should still be available. Additional info: My understanding is that changing the Lifecycle Environment or Content View of a hostgroup does not change existing hosts, only future ones, however changing the puppet module assignments will change existing hosts too. We need to reconcile these two behaviours - for example, what happens if you change the content view in the hostgroup to one that does not contain the existing modules?
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.
Connecting redmine issue http://projects.theforeman.org/issues/3551 from this bug
Upstream bug component is Provisioning
This is still a problem with Sat6.1.3. Changing the Content View and puppet environments does not keep the classes, even if the classes are available in the both contentview/puppetenvironment UseCase is when you upgrade the Host to a ContentView that has a newer release: Before CV-1.0 Change to CV-1.1 Then the puppet module with the name product-cv-module that is availabel in both Contentviews is not kept, requiring the user to re-associate all puppet modules. This is a tedious task if you have 10+ puppet modules to associate.
Per 6.3 planning, moving out non acked bugs to the backlog
Upstream bug component is Configuration Management
Upstream bug component is Puppet
Upstream bug assigned to sgraessl
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/3551 has been resolved.
The fix to this bug will be delivered with release 6.3 of Satellite.