Would it be possible to... ( I suppose that this is an enhancement request )... automatically do the following on a client-side manifest failure: 1. Wipe localconfig.yaml and state.yaml and try again (seems to fix most things for me) 2. Revert to a last known good configuration if all else fails. Thanks, Trevor _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Apr 18, 2007, at 12:59 PM, Trevor Vaughan wrote:> Would it be possible to... ( I suppose that this is an enhancement > request )... automatically do the following on a client-side > manifest failure: > > 1. Wipe localconfig.yaml and state.yaml and try again (seems to fix > most things for me) > 2. Revert to a last known good configuration if all else fails.Theoretically, state.yaml has somewhat important information in it (like the last known checksums for files being managed), so you wouldn''t normally want to wipe it, but I know it sometimes gets corrupted. I just looked at the code, and it looks like (foolishly) I''m caching the configuration before I see if it''s valid, which is definitely a bug. Would fixing that do most of what you want? -- Between two evils, I always pick the one I never tried before. -- Mae West --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Hmm...that would probably fix things nicely. I''ve just had some strange cases where state.yaml seems to have strange corruption errors that magically disappear once I wipe it. However, I can''t seem to wipe the state without also wiping localconfig and vice versa if I want puppet to work properly. Are these files truly tightly coupled? Is there any way to decouple them? Thanks, Trevor On 4/18/07, Luke Kanies <luke@madstop.com> wrote:> > On Apr 18, 2007, at 12:59 PM, Trevor Vaughan wrote: > > > Would it be possible to... ( I suppose that this is an enhancement > > request )... automatically do the following on a client-side > > manifest failure: > > > > 1. Wipe localconfig.yaml and state.yaml and try again (seems to fix > > most things for me) > > 2. Revert to a last known good configuration if all else fails. > > Theoretically, state.yaml has somewhat important information in it > (like the last known checksums for files being managed), so you > wouldn''t normally want to wipe it, but I know it sometimes gets > corrupted. > > I just looked at the code, and it looks like (foolishly) I''m caching > the configuration before I see if it''s valid, which is definitely a > bug. Would fixing that do most of what you want? > > -- > Between two evils, I always pick the one I never tried before. -- > Mae West > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >_______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Apr 19, 2007, at 7:16 AM, Trevor Vaughan wrote:> Hmm...that would probably fix things nicely. > > I''ve just had some strange cases where state.yaml seems to have > strange corruption errors that magically disappear once I wipe it. > However, I can''t seem to wipe the state without also wiping > localconfig and vice versa if I want puppet to work properly. > > Are these files truly tightly coupled? Is there any way to > decouple them?Are you running an older version? These files are not coupled, but someone recently found a bug (fixed in 0.22.2) that caused a failure if you only removed localconfig.yaml without also removing state.yaml. That is, the files aren''t coupled functionally, but the code was implicitly making one dependent on the other. Newer versions shouldn''t have this trouble. I''ve fixed the code so that only valid configurations are cached. -- 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
Ah! I appear to be running 0.22.1. May I apologize with a resounding "D''oh". Thanks, Trevor On 4/19/07, Luke Kanies <luke@madstop.com> wrote:> > On Apr 19, 2007, at 7:16 AM, Trevor Vaughan wrote: > > > Hmm...that would probably fix things nicely. > > > > I''ve just had some strange cases where state.yaml seems to have > > strange corruption errors that magically disappear once I wipe it. > > However, I can''t seem to wipe the state without also wiping > > localconfig and vice versa if I want puppet to work properly. > > > > Are these files truly tightly coupled? Is there any way to > > decouple them? > > Are you running an older version? > > These files are not coupled, but someone recently found a bug (fixed > in 0.22.2) that caused a failure if you only removed localconfig.yaml > without also removing state.yaml. That is, the files aren''t coupled > functionally, but the code was implicitly making one dependent on the > other. Newer versions shouldn''t have this trouble. > > I''ve fixed the code so that only valid configurations are cached. > > -- > 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 > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >_______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users