Issue #9410 has been updated by Stefan Schulte.
It looks like the yumrepo type uses a class variable (@inifile) that is used to store an in-memory representation of the yum repositories but never refreshes it between puppetruns. So if you run puppet as a daemon (and not out of cron for example) you'll notice the described behaviour. Maybe this is best solved in #8758? ---------------------------------------- Bug #9410: yumrepo type does notice changes https://projects.puppetlabs.com/issues/9410 Author: Jascha Lee Status: Needs More Information Priority: Normal Assignee: James Turnbull Category: yumrepo Target version: Affected Puppet version: 2.6.6 Keywords: Branch: If the yum repo config file changes or disappears after the initial puppet run in which it was created or modified, subsequent puppet runs will not notice. The local change will remain (inconsistent with the catalog) and/or the removed file will not be reconstructed. It was suggested that indentation of multiple gpgkey values might be at play, but this happens even with a single gpgkey value. class yum { yumrepo { "tivo-coxrtltivoqa2sp01.tivo.com": descr => "TiVo repo coxrtltivoqa2sp01.tivo.com", baseurl => "http://$yumvar_reponame/yum/rpms";, gpgkey => "http://$yumvar_reponame/yum/GPG/RPM-GPG-KEY-MySQL";, gpgcheck => "1", enabled => "1"; } } -- 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.
