-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(BKR-1600) Default puppet settings to main
section
#118
Conversation
If puppet.conf contained a setting without a preceding section, as can happen due to PUP-4755, then the 'lay_down_new_puppet_conf' method created a 'global' section for that setting, however, that is not a valid puppet section name. Specify the default section name as 'main' so it matches puppet's behavior.
This is still failing on 040_ValidateSignCert.rb for me (agent version: 1.10.15, server version: 2.8.1).
I'll try to check this further. |
Reverting the hostname setting part fixed this: e685f3a#diff-b33b2ccf419a7e2febd4be50ced7c892R22 Looks like when @joshcooper, what do you think? Can we use |
I don't think we can use |
This is expected in puppet 4.x, since we only fixed the issue in 5.x (to ensure a section is always added).
When the
This is how I'm testing this:
I get similar results with a different test:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joshcooper you're right... the only thing I was missing was the bundle update
step, I thought setting the beaker_puppet path would suffice.
I can confirm this works. Thanks! 👍
If puppet.conf contained a setting without a preceding section, as can happen
due to PUP-4755, then the 'lay_down_new_puppet_conf' method created a 'global'
section for that setting, however, that is not a valid puppet section name.
Specify the default section name as 'main' so it matches puppet's behavior.