The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #1122

puppet should honor one major version release ago

Added by Ryan Dooley over 6 years ago. Updated over 6 years ago.

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

0%

Category:executables
Target version:0.24.3
Affected Puppet version:0.25.4 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

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.

History

#1 Updated by Luke Kanies over 6 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 over 6 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