Okay, here is the newest strangeness. Mind this was all working with puppet 2.24.1, I now get the following strange error: puppetd[5720]: (//Node[workstation]/common-root/File[/root/.ssh/authorized_keys]/ensure) change from absent to file failed: Could not set file on ensure: No such file or directory - /root/.ssh/authorized_keys.puppettmp at /srv/manifests/classes/set-root.pp:34 puppetd[5720]: (//Node[workstation]/common-root/File[/root/.ssh/known_hosts]/ensure) change from absent to file failed: Could not set file on ensure: No such file or directory - /root/.ssh/known_hosts.puppettmp at /srv/manifests/classes/set-root.pp:45 The file extensions of .puppettmp to both files is new and appears to be what is causing the failure. No changes where made to the common-root class or set-root definition before or after the upgrade. Evan P.S> Feeling a bit like a squeaky wheel right know. --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Apr 1, 2008, at 4:33 PM, Evan Hisey wrote:> > Okay, here is the newest strangeness. Mind this was all working with > puppet 2.24.1, I now get the following strange error: > > puppetd[5720]: > (//Node[workstation]/common-root/File[/root/.ssh/authorized_keys]/ > ensure) > change from absent to file failed: Could not set file on ensure: No > such file or directory - /root/.ssh/authorized_keys.puppettmp at > /srv/manifests/classes/set-root.pp:34 > puppetd[5720]: (//Node[workstation]/common-root/File[/root/.ssh/ > known_hosts]/ensure) > change from absent to file failed: Could not set file on ensure: No > such file or directory - /root/.ssh/known_hosts.puppettmp at > /srv/manifests/classes/set-root.pp:45 > > The file extensions of .puppettmp to both files is new and appears to > be what is causing the failure. No changes where made to the > common-root class or set-root definition before or after the upgrade.I don''t think that behaviour has changed recently, but maybe it has. That''s Puppet doing atomic writes, which are generally a good idea. This way if it gets interrupted in the middle, you won''t have a corrupted file. I''m skeptical that that behaviour is new. It might be slightly different, but I don''t think it actually is. At least, not for the normal file type.> > P.S> Feeling a bit like a squeaky wheel right know.Better to get the problems out in the open. -- Silence is a text easy to misread. -- A. A. Attanasio, ''The Eagle and the Sword'' --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
> > The file extensions of .puppettmp to both files is new and appears to > > be what is causing the failure. No changes where made to the > > common-root class or set-root definition before or after the upgrade. > > I don''t think that behaviour has changed recently, but maybe it has. > That''s Puppet doing atomic writes, which are generally a good idea. > This way if it gets interrupted in the middle, you won''t have a > corrupted file. > > I''m skeptical that that behaviour is new. It might be slightly > different, but I don''t think it actually is. At least, not for the > normal file type.> > P.S> Feeling a bit like a squeaky wheel right know. > > > Better to get the problems out in the open. >More digging later, it looks like the error was actually the result of client/server mismatch early that seems to have caused the removal of the /root/.ssh directory. Perhaps a change in the way write failures are reported might make it easier to track down what is actually triggering the errors. I have foudn that errors triggerd by poor permission on the fileserver or missing dir. both tend to have obtuse errors for those not seeing them before. Tomorrow I will test another bootstrap and see if all teh changes now work happily. Evan --~--~---------~--~----~------------~-------~--~----~ 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-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---