I've created a custom augeas schema to handle up2date sources, and I'm using puppet to deploy it; followed by the use of augeas to add lines to the /etc/sysconfig/rhn/sources file. I do have a requirement on all augeas lines that the File["rhnsources.aug"] be deployed first, however I just noticed this on a fresh kickstart of my test system:
notice: Starting catalog run notice: /:main/augeas::custom/File[rhnsources.aug]/ensure: created err: /:main/repos::default/Repos::Rhn_source[epel-i386]/Augeas[add-repos-epel-i386]: Failed to retrieve current state of resource: unknown error - Failed to initialize Augeas notice: /:main/repos::default/Repos::Rhn_source[epel-i386]/Augeas[update-repos-epel-i386]: Dependency augeas[add-repos-epel-i386] has 1 failures warning: /:main/repos::default/Repos::Rhn_source[epel-i386]/Augeas[update-repos-epel-i386]: Skipping because of failed dependencies err: /:main/repos::default/Repos::Rhn_source[custom-x86_64]/Augeas[add-repos-custom-x86_64]: Failed to retrieve current state of resource: unknown error - Failed to initialize Augeas When puppetd is re-run, it creates all the entries correctly, as expected. My question is: how can I correct this? I'd like it all to work in a single pass, and not have to re-run puppetd when deploying custom augeas schemas. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
