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:
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?
Comment 1RHEL Program Management
2014-10-30 16:13:16 UTC
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 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.