How to make sure a config file haven't changed in an OS upgrade?

[Jasmine Lognnes]

Dear all =)

I have a CentOS5 node that I would like to upgrade to CentOS6, but how can I trust that my CentOS5 node manifest won't destroy the config files on the CentOS6 node because the config files have changed from CentOS5 to CentOS6?

How do you prevent this kind of situation? Do you make a copy of all the CentOS5 config files and diff them with the CentOS6 ones? If, how do you do that in an automated way?

Kindest regards

Jasmine =)

[Dan White]

http://docs.puppetlabs.com/facter/latest/core_facts.html#operatingsystemrelease

http://docs.puppetlabs.com/facter/latest/core_facts.html#operatingsystemmajrelease

http://docs.puppetlabs.com/references/latest/function.html#versioncmp

and an example:

http://www.mail-archive.com/puppet-users%40googlegroups.com/msg18460.html

And, if you have filebucket turned on, you can back out any changes made by a run.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/37b6aaa9-e4ba-4f45-a743-be37c1a682e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” 
Bill Waterson (Calvin & Hobbes)

[Jasmine Lognnes]

Interesting!

Would it be possible to only apply the change, if the config file have a certain checksum?

[Jakov Sosic]

You can use facter variables to control which for example template you
will use depending on the major version of OS.

Similar issue can be observed with versions of software - for example if
you try to manage Zabbix, there are versions 1.8, 2.0, 2.2 and soon
there will be 2.4. With Cobbler for example, there is 2.2 and 2.4.

The way I do it is to test new version in a dev environement and rewrite
modules/templates with version-aware configs as needed... It's an
unpleasant task, but on the upside it has to be done only once.

[Trevor Vaughan]

Going from Cent5 to Cent6 you are almost guaranteed to have configuration file changes.

As Jakov points out, the only sure fire way of doing this is to do a test upgrade and see what breaks.

When you run puppet, you'll get a list of the files that have been modified.

Also, doing upgrades between major releases is not generally recommended and may cause unforseen issues in the future. A fresh kick is best if possible.

Trevor

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/37b6aaa9-e4ba-4f45-a743-be37c1a682e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvau...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

[Felix Frank]

Hi,

another safe way to proceed is to disable automatic agent runs and check
for breakages after the update using puppet agent/apply --noop.

Cheers,
Felix

On 04/20/2014 02:38 AM, Jasmine Lognnes wrote:

[Dirk Heinrichs]

Am 21.04.2014 00:17, schrieb Trevor Vaughan:

Also, doing upgrades between major releases is not generally recommended and may cause unforseen issues in the future. A fresh kick is best if possible.

... if running RHEL/CentOS (or upgrade by booting from CD/DVD). Debian derivatives, OTOH, support in-place upgrades.

Bye...

    Dirk

--

Dirk Heinrichs, Senior Systems Engineer, Engineering Solutions
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Tel: +49 2226 1596666 (Ansage) 1149
Email: d...@recommind.com
Skype: dirk.heinrichs.recommind
www.recommind.com