-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > It does seem fixed in 2.6.1rc3, however 0.25.5 it is still happens. > Has there been a convergence of opinion on how to roll out 2.6.x? > Server first then clients? Clients first then the server? > Everything at once? (that is hard obviously)
always update master first. "It is also important to note when upgrading that not all versions are backwards compatible. Newer clients may not work with older servers and vice-versa. Where possible backwards-compatibility is maintained but it?s not always totally successful. The best approach is to ensure your master and clients are the same version. When upgrading it is also recommended that you upgrade your master first." http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyAGW4ACgkQbwltcAfKi38jMQCfdBKAE1Iwyoytcb1i5liO5ZGB P7sAn0nwH0duT0RLJXtUUWmOkc0gAjkh =3Ajp -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
