Description of problem:
I imported the puppetlabs-ntp and puppetlabs-stdlib classes. On first run, all was fine. Then, I wanted to change the 'server' parameter, so I opened the smart parameters tab of the ntp class, and found all classes were marked 'overriden'.
I only set the 'server' parameter, but Puppet barfed that all parameters were now filled with empty strings, and thus didn't match the expected types:
From the log on the satellite (which was also the puppet client in my case):
puppetlabs/puppetserver/puppetserver.log: parameter 'enable_mode7' expects a Boolean value, got String
puppetlabs/puppetserver/puppetserver.log: parameter 'iburst_enable' expects a Boolean value, got String
puppetlabs/puppetserver/puppetserver.log: parameter 'keys_enable' expects a Boolean value, got String
YAML output on the Satellite:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. import puppetlabs-ntp in new satellite
2. run puppet
3. go to smart parameters tab for ntp class
all parameters are marked as overriden
None should be
Module I imported: https://forge.puppet.com/puppetlabs/ntp
It happens only with that module, but I do not know whether that is because it was the first one I used (and that was also the case for the person in that thread mentioned above), or because it's really only that module that triggers it.
I had this same issue and can confirm it only seems to happen with that module, other ones i have tried (like puppetlabs apache) don't seem to have this issue.
Does this behavior exist also on 6.2?
Does it truely only happen with this module or could it be a case of it happens with the first module used?
Created redmine issue https://projects.theforeman.org/issues/24355 from this bug
Upstream bug assigned to orabin
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/24355 has been resolved.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.