it seems that puppet refuse to run in the new version. It fails on the line: err: Could not apply complete configuration: Unknown configuration parameter :lockdir the client is .22.1 and server still .22.0 -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Feb 1, 2007, at 4:42 PM, ADNET Ghislain wrote:> it seems that puppet refuse to run in the new version. It fails on > the line: > > err: Could not apply complete configuration: Unknown configuration > parameter :lockdir > > > the client is .22.1 and server still .22.0Oops. Yeah, I realized that that directory is not used anywhere in Puppet, so I removed it. You should be able to safely remove the parameter. -- It''s not to control, but to protect the citizens of Singapore. In our society, you can state your views, but they have to be correct. -- Ernie Hai, co-ordinator of the Singapore Government Internet Project --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
> > Oops. Yeah, I realized that that directory is not used anywhere in > Puppet, so I removed it. > > You should be able to safely remove the parameter.it seems that all my hosts stopped working since then, i have to manualy connect and remove the parametermanualy from all nodes so puppet work again :( -- Cordialement, Ghislain ADNET. AQUEOS. _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
ADNET Ghislain wrote:>> Oops. Yeah, I realized that that directory is not used anywhere in >> Puppet, so I removed it. >> >> You should be able to safely remove the parameter. > > > it seems that all my hosts stopped working since then, i have to > manualy connect and remove the parametermanualy from all nodes so > puppet work again :(I had something similar happen too, although I caught it before all of my hosts starting falling over. Next time is there any chance you could make it warn for a few versions before just bombing out? It''s a surplus deprecated option, it''s not exactly something that should cause the clients to fall flat on their faces. Mark
> Next time is there any chance you could make it warn for a few versions > before just bombing out? > > It''s a surplus deprecated option, it''s not exactly something that should > cause the clients to fall flat on their faces.would be great, using puppet make us so lazzzy i can''t go to my ssh loop changing the file eheh ! anyway i would like to tell Luke that puppet is really an incredible tool to me, so thanks again for making me lazy ! ;) -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
ADNET Ghislain wrote:> >> Next time is there any chance you could make it warn for a few >> versions before just bombing out? >> It''s a surplus deprecated option, it''s not exactly something that >> should cause the clients to fall flat on their faces. > > > would be great, using puppet make us so lazzzy i can''t go to my ssh > loop changing the file eheh !The ssh loop on 40 (ish) machines that aren''t always on, can be a little repetitive. ;)> anyway i would like to tell Luke that puppet is really an incredible > tool to me, so thanks again for making me lazy ! ;)Now that I definitely agree with. It''s got bugs, but it''s not hit version1 yet, and Luke does do quite a good job of hitting the bugs in a reasonable time frame. It''s turning into a wonderful little system for maintaining the assortment of (Fedora) Linux desktops I''ve got scattered around the department. Much nicer than having to build and maintain custom RPMs to rewrite the config files. Mark
On Feb 12, 2007, at 5:32 AM, Mark Chappell wrote:> > I had something similar happen too, although I caught it before all of > my hosts starting falling over. > > Next time is there any chance you could make it warn for a few > versions > before just bombing out? > > It''s a surplus deprecated option, it''s not exactly something that > should > cause the clients to fall flat on their faces.Part of the problem was that Puppet wasn''t using it at all, so I didn''t so much deprecate it as just remove the already-unused parameter. Another part of the problem was that I didn''t realize that the RPM version of the config file set that parameter. Lastly, it was a bad decision on my part to fail during parsing the configuration file; puppetd should generally ignore this kind of warning, which it now does (thanks to Jeff McCune''s work). I normally do my best to provide warnings for a few versions; in this case, I just checked the code and verified that nothing was using the parameter, so it didn''t seem necessary. Clearly I was wrong. -- If there is anything the nonconformist hates worse than a conformist, it''s another nonconformist who doesn''t conform to the prevailing standard of nonconformity. --Bill Vaughan --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
> I normally do my best to provide warnings for a few versions; in this > case, I just checked the code and verified that nothing was using the > parameter, so it didn''t seem necessary. Clearly I was wrong. >thanks to you and Jeff McCune for the fix, we allways get beat by the thing we thinked they would never do :) -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users