Hide Forgot
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.