Issue #16218 has been updated by eric sorenson. Status changed from Unreviewed to Needs More Information Assignee set to James Patterson
As RI said, please include --debug output from the client. Also note if the /etc/yum.repos.d directory is not created before the first yumrepo resource is evaluated, the repos will be added to yum.conf. ---------------------------------------- Bug #16218: puppet abandons some changes on a puppetd restart https://projects.puppetlabs.com/issues/16218#change-70413 Author: James Patterson Status: Needs More Information Priority: Normal Assignee: James Patterson Category: Target version: Affected Puppet version: 2.7.17 Keywords: Branch: I have a special stage that configures puppet and writes some yum repos. The puppet config part has a notify that restarts puppet. The yum part just writes some .repo files to disk using the repo class. Although the log says the repo changes were made, they weren't - I can't see the .repo files on disk. I strongly suspect that the puppetd restart is causing these changes to not be commited properly. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
