Dimitri Tischenko The long-term solution is to not run puppet device as root. I'd love to hear your opinion about that. Meanwhile I've got some code changes in https://github.com/puppetlabs/puppet/pull/7483 which will likely fix the initialisation problem. I'm a bit concerned that it went away with 6.4, because that means that there is sometihng else going on that I do not fully understand yet (or I have messed up my testing).
Under certain circumstances `puppet device` would get confused with directory permissions when initialising new device certificates. This fixes `puppet device` to always initialise the ssl directories with the correct permissions.
Hey, there's a really nasty looking merge conflict in `lib/puppet/application/device.rb` trying to merge 5.5.x up into 6.0.x, and it looks like it's from commits you had a hand in. Could you take a crack at resolving that? There's also some conflicts in `pip` related files that aren't 100% straight-forward, but feel free to ping @jorie or myself on that.
David Mallon the promotions happen automatically during merge-ups. Merge-ups are done by Jenkins once the tests pass for a specific branch. Currently, the agent CI is still stuck because of this issue: https://tickets.puppetlabs.com/browse/QENG-7269
Hi David Schmitt this was merged into master and will be part of the 6.5.0 release. Can you please let us know if this is resolved by closing the ticket ?
Hi David Schmitt this was merged into master and will be part of the 6.5.0 release. Can you please let us know if this is resolved by closing the ticket ?
The commit has acceptance tests. If those pass, the problem won't be seen by customers any more.