On Nov 30, 10:19 pm, James Turnbull <[email protected]> wrote: > Jonathan wrote: > > James- > > > I literally said those exact words. But on a whim I changed then order > > and it works correctly, every time. I haven't had a chance to dig deeper > > yet, so I'm not sure if the issue is in the namespace provider, but the > > patch definitely fixes it. > > > Try out the patch using the same steps below. It'll work, I swear :-) > > It's still not right way to fix it ... even if it does. > > I'd like to dig a bit deeper I think. > > Regards > > James Turnbull > > -- > Puppet Labs -http://www.puppetlabs.com > C: 503-734-8571
After working with James, it was determined that my solution is not the cleanest. The issue will need to be addressed in the provider, changing the order of the resources in a more documentable fashion. The nameservice.set and objectadd.modifycmd methods both look like good places to start. Would it be more worthwhile to simply write a new provider for useradd which isn't reliant on nameservice? -- Jonathan -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
