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.
Created attachment 1482600[details]
test module with one smart class parameter
Description of problem:
Demoting puppet version is not reflected on the Satellite webui.
Version-Release number of selected component (if applicable): Satellite 6.3 + puppet3
How reproducible: Always
Steps to Reproduce:
1. Publish a puppet module into a CV version containing one smart class parameter into some life cycle environment.
2. Add puppet module version that contains 2 or more smart class parameters into a new CV version and promote it into the same set of lifecycle environments.
3. Now if you go to satellite webui, "Configure" --> "Smart Class Parameter", then you will see that both the smart class parameters are associated with all the related puppet environments.
4. Now promote any one life cycle environment from CV version 2.0 back to CV version 1.0 and see the smart class parameters in the webui. You will see that the "smart class parameter" associations continue to be the same as before.
Actual results:
Demoting from puppet module version having 2 smart class parameters to the puppet module version having one smart class parameter does not get reflected in the satellite webui.
Expected results:
Satellite webui should remove the smart class parameter association with the demoted puppet environment.
Additional info:
- I tested this both for Satellite 6.3 + puppet3 and Satellite 6.3 + puppet4 and this issue is only observed for puppet3
- This issue is reproducible for the puppet modules that were provided by the customer and also the test puppet modules that I wrote. I attaching both on the bz. (Will make my test puppet modules as public)
- This issue is only for the webui/apache. The filesystem (/etc/puppet/environments) on the Satellite shows the correct puppet modules in their respective puppet environments. Trying to "import from Satellite" option under "Configure" --> "Classes" or "Environments" does not help in resolving the issue.
Mihir,
Thank you for submitting this bugzilla and providing the detailed analysis/details.
As of Satellite 6.4, the supported version of puppet will be Puppet 5. Since this issue is only present with Puppet 3 and we do not have plans to resolve it within the Satellite 6.3.z timeframe, we are closing the request.
If the issue surfaces with Puppet 5, please feel free to re-open this bugzilla.
Created attachment 1482600 [details] test module with one smart class parameter Description of problem: Demoting puppet version is not reflected on the Satellite webui. Version-Release number of selected component (if applicable): Satellite 6.3 + puppet3 How reproducible: Always Steps to Reproduce: 1. Publish a puppet module into a CV version containing one smart class parameter into some life cycle environment. 2. Add puppet module version that contains 2 or more smart class parameters into a new CV version and promote it into the same set of lifecycle environments. 3. Now if you go to satellite webui, "Configure" --> "Smart Class Parameter", then you will see that both the smart class parameters are associated with all the related puppet environments. 4. Now promote any one life cycle environment from CV version 2.0 back to CV version 1.0 and see the smart class parameters in the webui. You will see that the "smart class parameter" associations continue to be the same as before. Actual results: Demoting from puppet module version having 2 smart class parameters to the puppet module version having one smart class parameter does not get reflected in the satellite webui. Expected results: Satellite webui should remove the smart class parameter association with the demoted puppet environment. Additional info: - I tested this both for Satellite 6.3 + puppet3 and Satellite 6.3 + puppet4 and this issue is only observed for puppet3 - This issue is reproducible for the puppet modules that were provided by the customer and also the test puppet modules that I wrote. I attaching both on the bz. (Will make my test puppet modules as public) - This issue is only for the webui/apache. The filesystem (/etc/puppet/environments) on the Satellite shows the correct puppet modules in their respective puppet environments. Trying to "import from Satellite" option under "Configure" --> "Classes" or "Environments" does not help in resolving the issue.