The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Bug #1122

puppet should honor one major version release ago

Added by Ryan Dooley about 8 years ago. Updated about 8 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Luke Kanies% Done:


Target version:0.24.3
Affected Puppet version:0.25.4 Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


In my current setup I typically upgrade clients first and then the puppetmaster (which I admit is kind of backwards….) so it would be nice if 0.N clients would honor or adapt to 0.M masters and the reverse would be nice as well.

That way I could roll out a 0.24 client while still on a 0.23 server or update a 0.23 server to 0.24 before upgrading 0.23 clients.


#1 Updated by Luke Kanies about 8 years ago

  • Status changed from 1 to 2

I agree. I’m trying to figure out if I can actually do this for this release. Not promising anything, just agreeing philosophically.

#2 Updated by Luke Kanies about 8 years ago

  • Status changed from 2 to Closed
  • 7 set to fixed

The specific bug in this case is filed appropriately, so this is more of a philosophical bug. I’ll consider it closed, since I’m convinced.

Also available in: Atom PDF