Feature #14861
Client backward compatability
| Status: | Needs Decision | Start date: | 06/06/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
Description
Would like to see the puppet client be backward compatible with older puppet-master servers. The reason is that admins are likely to have the puppet master be a more stable version of Linux, namely RHEL or Centos. If there is a need or desire to have a more bleeding edge or newer flavor like Fedora or Gentoo as a client, it is not possible under current circumstances.
History
#1
Updated by Kelsey Hightower about 1 year ago
- Status changed from Unreviewed to Needs Decision
Maurice,
Thanks for this feature request. As you may already know, our current policy around backwards-compatibility is this:
It is also important to note when upgrading that not all versions are backwards compatible. Newer agents may not work with older masters and vice-versa. Where possible backwards-compatibility is maintained but it’s not always totally successful. We strongly recommend ensuring your master and agents are the same version.
When upgrading it is also strongly recommended that you upgrade your master first and then your agents. Earlier agents usually work with later masters but later agents frequently have issues with earlier master versions. For example 0.24.8 agents will work with 2.6.6 masters but 2.6.6 agents may have unpredictable results with a 0.24.8 master.
I’m going place this ticket in “Needs Decision” so that we take the time to review our current policy.