[Puppet Users] Re: ssh_authorized_key completely ignoring require
It's supposed to be fixed in 0.25, which is now rc1. I haven't tried 0.25 yet seph Mike Harding mvhard...@gmail.com writes: I am just starting with puppet, and the intended use was to manage ssh keys. Is there an intended release to fix this, or some other way to get it working? On Jul 17, 1:14 pm, seph s...@directionless.org wrote: As someone whose actively setting up and deploying puppet on new machines, this bug is a huge annoyance for me. Instead of having a simple recipe, my process involves invoking puppet to create users, then invoking puppet to add keys. It's frustrating that this still isn't fixed in the released versions. seph Chris Blumentritt cblum...@gmail.com writes: I have run into this problem today trying to stand up some new servers. On Tue, Apr 21, 2009 at 11:44 PM, Andrew Shafer and...@reductivelabs.comwrote: Scott, Can you pastie the simplest code to reproduce and maybe attach the files created by --graph to see what the relationships look like. Is anyone else seeing a problem like this? On Tue, Apr 21, 2009 at 9:02 PM, Scott scott...@gmail.com wrote: Hi, so I'm running into a problem since upgrading to 0.24.8 where puppet is trying to create an authorized key for users that don't exist because it doesn't do the require ( require = /etc/passwd ) first. I've tried making the require a default parameter for ssh_autohrized_key (yes, in the same scope), I've tried making the passwd file a requirement for every ssh_authorized_key and I've tried to use before with the passwd resource ( before = Class [ users::ssh_keys ] ) and yet puppet insists on trying to create the key before doing any of the prerequisites. One other note, thessh_authorized_keyisn't always for the same person, so it's not a particular key that's causing the problem. Also, this was never a problem with 0.24.7. Cheers, Scott --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: ssh_authorized_key completely ignoring require
I am just starting with puppet, and the intended use was to manage ssh keys. Is there an intended release to fix this, or some other way to get it working? On Jul 17, 1:14 pm, seph s...@directionless.org wrote: As someone whose actively setting up and deploying puppet on new machines, this bug is a huge annoyance for me. Instead of having a simple recipe, my process involves invoking puppet to create users, then invoking puppet to add keys. It's frustrating that this still isn't fixed in the released versions. seph Chris Blumentritt cblum...@gmail.com writes: I have run into this problem today trying to stand up some new servers. On Tue, Apr 21, 2009 at 11:44 PM, Andrew Shafer and...@reductivelabs.comwrote: Scott, Can you pastie the simplest code to reproduce and maybe attach the files created by --graph to see what the relationships look like. Is anyone else seeing a problem like this? On Tue, Apr 21, 2009 at 9:02 PM, Scott scott...@gmail.com wrote: Hi, so I'm running into a problem since upgrading to 0.24.8 where puppet is trying to create an authorized key for users that don't exist because it doesn't do the require ( require = /etc/passwd ) first. I've tried making the require a default parameter for ssh_autohrized_key (yes, in the same scope), I've tried making the passwd file a requirement for every ssh_authorized_key and I've tried to use before with the passwd resource ( before = Class [ users::ssh_keys ] ) and yet puppet insists on trying to create the key before doing any of the prerequisites. One other note, thessh_authorized_keyisn't always for the same person, so it's not a particular key that's causing the problem. Also, this was never a problem with 0.24.7. Cheers, Scott --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: ssh_authorized_key completely ignoring require
As someone whose actively setting up and deploying puppet on new machines, this bug is a huge annoyance for me. Instead of having a simple recipe, my process involves invoking puppet to create users, then invoking puppet to add keys. It's frustrating that this still isn't fixed in the released versions. seph Chris Blumentritt cblum...@gmail.com writes: I have run into this problem today trying to stand up some new servers. On Tue, Apr 21, 2009 at 11:44 PM, Andrew Shafer and...@reductivelabs.comwrote: Scott, Can you pastie the simplest code to reproduce and maybe attach the files created by --graph to see what the relationships look like. Is anyone else seeing a problem like this? On Tue, Apr 21, 2009 at 9:02 PM, Scott scott...@gmail.com wrote: Hi, so I'm running into a problem since upgrading to 0.24.8 where puppet is trying to create an authorized key for users that don't exist because it doesn't do the require ( require = /etc/passwd ) first. I've tried making the require a default parameter for ssh_autohrized_key (yes, in the same scope), I've tried making the passwd file a requirement for every ssh_authorized_key and I've tried to use before with the passwd resource ( before = Class [ users::ssh_keys ] ) and yet puppet insists on trying to create the key before doing any of the prerequisites. One other note, the ssh_authorized_key isn't always for the same person, so it's not a particular key that's causing the problem. Also, this was never a problem with 0.24.7. Cheers, Scott --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: ssh_authorized_key completely ignoring require
I have run into this problem today trying to stand up some new servers. On Tue, Apr 21, 2009 at 11:44 PM, Andrew Shafer and...@reductivelabs.comwrote: Scott, Can you pastie the simplest code to reproduce and maybe attach the files created by --graph to see what the relationships look like. Is anyone else seeing a problem like this? On Tue, Apr 21, 2009 at 9:02 PM, Scott scott...@gmail.com wrote: Hi, so I'm running into a problem since upgrading to 0.24.8 where puppet is trying to create an authorized key for users that don't exist because it doesn't do the require ( require = /etc/passwd ) first. I've tried making the require a default parameter for ssh_autohrized_key (yes, in the same scope), I've tried making the passwd file a requirement for every ssh_authorized_key and I've tried to use before with the passwd resource ( before = Class [ users::ssh_keys ] ) and yet puppet insists on trying to create the key before doing any of the prerequisites. One other note, the ssh_authorized_key isn't always for the same person, so it's not a particular key that's causing the problem. Also, this was never a problem with 0.24.7. Cheers, Scott --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Puppet Users] Re: ssh_authorized_key completely ignoring require
Scott, Can you pastie the simplest code to reproduce and maybe attach the files created by --graph to see what the relationships look like. Is anyone else seeing a problem like this? On Tue, Apr 21, 2009 at 9:02 PM, Scott scott...@gmail.com wrote: Hi, so I'm running into a problem since upgrading to 0.24.8 where puppet is trying to create an authorized key for users that don't exist because it doesn't do the require ( require = /etc/passwd ) first. I've tried making the require a default parameter for ssh_autohrized_key (yes, in the same scope), I've tried making the passwd file a requirement for every ssh_authorized_key and I've tried to use before with the passwd resource ( before = Class [ users::ssh_keys ] ) and yet puppet insists on trying to create the key before doing any of the prerequisites. One other note, the ssh_authorized_key isn't always for the same person, so it's not a particular key that's causing the problem. Also, this was never a problem with 0.24.7. Cheers, Scott --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
