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 you have a Puppet module that changed parameters (e.g. version 1 had paramA, version 2 renamed it to param_A) and promote a CV containing this module, there is a timeframe between the module is updated in /etc/puppet/environments/KT_… and the Puppet integration of Satellite/Katello/Foreman updates the hosts that have this environment where the module on disk would not match the parameters passed from Foreman, thus resulting in failed puppet runs.
Version-Release number of selected component (if applicable):
satellite-6.2.3-1.0.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. create a puppet module with a parameter and upload it to satellite
2. do the necessary to assign the module to a host and override the parameter to a non-default value
3. update the module to remove or rename the parameter that was overriden
4. monitor /etc/puppet/enviroments to have the new module, but the overall publish/promote task in satellite not yet finished
5. run puppet agent on the host
Actual results:
puppet fails, as is cannot set a non-existing parameter
Expected results:
puppet runs successfully
Additional info:
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.