Issue #5554 has been updated by Nigel Kersten.
So we're happy with just saying we seem to be talking to something that doesn't understand us and not being specific about it being an older Puppet version? I'm not entirely sure how we'd distinguish between a 0.24.x Puppet server and a completely foreign daemon without keeping legacy code around to talk using the older protocol if we want to actually "detect the server version, report an appropriate error and fail." as per the initial request. ---------------------------------------- Feature #5554: Puppet agent/master compatibility should be mandated https://projects.puppetlabs.com/issues/5554 Author: James Turnbull Status: Needs more information Priority: Normal Assignee: James Turnbull Category: plumbing Target version: Affected Puppet version: Keywords: client backwards-compability master agent version Branch: Currently if a newer client tries to talk to an older master, for example a 0.25.x or 2.6.x client tries to talk to a 0.24.x master then there is little or no error message generated to indicate that this isn't a supported combination. So the client should detect the server version, report an appropriate error and fail. Similar structures for deprecating older clients should also be used. For example, perhaps in 2.7.x we might not support clients earlier than 0.24.8 and fail on connection from them? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
