On Sep 14, 2011, at 9:54 AM, Stoyan Nikolov wrote: > I have to add, if i run "apt-get upgrade -y" manually on a machine, and then > run the manifest again it works fine: > > (after running "apt-get upgrade -y" manually) > > root@agent3:~# puppetd --test > info: Caching catalog for agent3.sabrewolf.net > info: Applying configuration version '1316008127' > notice: //aguu/Exec[upgrade]/returns: executed successfully > notice: //aguu/Exec[update]/returns: executed successfully > warning: Value of 'preferred_serialization_format' (pson) is invalid for > report, using default (marshal) > notice: Finished catalog run in 34.87 seconds > > But I suspect that as soon as it will actually need to upgrade the > repositories it will fail again... ---- I do too but the problem isn't puppet... the problem is what happens from the command line executions of apt-get/aptitude/etc. which obviously leave apt in a state where it requires console interaction to resolve. If you stop using apt from command line, you won't have a problem with the puppet commands. If you use apt on the command line, you should learn to clean up after yourself and run things like 'apt-get -f install' (to install needed dependencies), 'apt-get autoremove' (to clean up unneeded packages), etc.
Also note that the package cache will get stale over time and you would need to run 'apt-get update' prior to running 'apt-get update -y' which is why I told you to note how I used 'require' in my puppet manifests to ensure that happens first. Craig -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
