Hello everyone, everytime I run on a puppet host: #puppet agent --test I see this commet: info: Applying configuration version ''000001'' then lets say I deploy a new package from my local repository, from which I would get a different configuration version. #puppet agent --test info: Applying configuration version ''000002'' ...question: is there a way to deploy back an older version, in this case ''000001''? and how? Thanks a lot! MrTeleBird -- 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 Tuesday, June 19, 2012 10:01:42 AM UTC-5, MrTeleBird wrote:> > Hello everyone, > > everytime I run on a puppet host: > #puppet agent --test > > I see this commet: > info: Applying configuration version ''000001'' > > then lets say I deploy a new package from my local repository, from > which I would get a different configuration version. > > #puppet agent --test > info: Applying configuration version ''000002'' > > ...question: is there a way to deploy back an older version, in this > case ''000001''? and how? >Not as far as I know, and anyway, it wouldn''t have the result you are probably thinking of. In particular, the message might be more precisely worded "applying *catalog* version <foo>". Applying an older catalog would not reliably revert the client to the configuration originally produced by that catalog -- that is, it would not revert changes applied in later catalogs. It cannot do so because earlier catalogs cannot contain full information about the content of later catalogs. What you can and should do is store all your manifests in a version-control system such as git or subversion. That will give you, among other things, the ability to revert your manifests to reflect some earlier point in time. Given identical node facts, the master will then compile and serve catalogs identical to those previously compiled from those manifests. (But that still won''t revert *node configurations* the way I suspect you were hoping.) John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/7ajldTVHP10J. 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.
Thanks a lot John! yes you got my point. I think I will better implement version control of my manifests, as you suggest. This will help for sure, but what I was wondering, was to revert node configurations. cheers On Tuesday, June 19, 2012 6:59:58 PM UTC+2, jcbollinger wrote:> > > > On Tuesday, June 19, 2012 10:01:42 AM UTC-5, MrTeleBird wrote: >> >> Hello everyone, >> >> everytime I run on a puppet host: >> #puppet agent --test >> >> I see this commet: >> info: Applying configuration version ''000001'' >> >> then lets say I deploy a new package from my local repository, from >> which I would get a different configuration version. >> >> #puppet agent --test >> info: Applying configuration version ''000002'' >> >> ...question: is there a way to deploy back an older version, in this >> case ''000001''? and how? >> > > Not as far as I know, and anyway, it wouldn''t have the result you are > probably thinking of. In particular, the message might be more precisely > worded "applying *catalog* version <foo>". Applying an older catalog > would not reliably revert the client to the configuration originally > produced by that catalog -- that is, it would not revert changes applied in > later catalogs. It cannot do so because earlier catalogs cannot contain > full information about the content of later catalogs. > > What you can and should do is store all your manifests in a > version-control system such as git or subversion. That will give you, > among other things, the ability to revert your manifests to reflect some > earlier point in time. Given identical node facts, the master will then > compile and serve catalogs identical to those previously compiled from > those manifests. (But that still won''t revert *node configurations* the > way I suspect you were hoping.) > > > John > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/o7-K5WCsNAYJ. 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.