You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm observing some unusual behavior with Puppet is version 2.7.18 running on Ubuntu 12.10.
When puppet is run manually with puppet agent -t or if the puppet daemon is restarted then the manifests runs fine, but after a few runs it starts throwing:
Could not prefetch network_config provider 'interfaces': Malformed debian interfaces file; cannot instantiate network_config resources
I suspect on machines configured to run the puppet agent from a cron job will not throw this error.
It's strange that it runs for a while, then suddenly fails. With respect to it staying failed, that seems to be a part of the failsafe mechanism that's triggering (https://github.com/adrienthebo/puppet-filemapper/blob/master/lib/puppetx/filemapper.rb#L248). The idea is that if a resource can't be flushed then we don't know what the state of the file is in, and shouldn't try to mangle it anymore. However, we should retry on a new puppet run, so this seems like a design oversight. Would you be able to try out a patch for the filemapper module to see if we can resolve the permanent failure mode issue?
I'm observing some unusual behavior with Puppet is version 2.7.18 running on Ubuntu 12.10.
When puppet is run manually with
puppet agent -t
or if the puppet daemon is restarted then the manifests runs fine, but after a few runs it starts throwing:I suspect on machines configured to run the puppet agent from a cron job will not throw this error.
This is similar to what's reported in #44
The text was updated successfully, but these errors were encountered: