Issue #15669 has been updated by Lee Lowder.
Saw this brought up in IRC recently, so thought I'd add a few comments. I've
got a 2.7.19 master and inadvertently wound up with a couple of 3.0.0 nodes.
I get a similar message when these nodes run, but as a warning.
The full output is available
Issue #15669 has been updated by Andrew Parker.
Assignee deleted (eric sorenson)
Target version deleted (3.x)
Feature #15669: A more helpful error message when the puppet master is at the
wrong version (2.7.x to 3.0)
Issue #15669 has been updated by eric sorenson.
Parent task deleted (#17017)
Feature #15669: A more helpful error message when the puppet master is at the
wrong version (2.7.x to 3.0)
https://projects.puppetlabs.com/issues/15669#change-74102
Author:
Issue #15669 has been updated by eric sorenson.
Parent task set to #17017
Feature #15669: A more helpful error message when the puppet master is at the
wrong version (2.7.x to 3.0)
https://projects.puppetlabs.com/issues/15669#change-73806
Author: Ben
Issue #15669 has been updated by eric sorenson.
Target version changed from 3.0.0 to 3.x
This would be good to have but I'm not going to block the 3.0.0 release on it;
we have been clear consistent about the upgrade master first strategy.
Mybe a FAQ item if the error is always the same.
Issue #15669 has been updated by eric sorenson.
Daniel thank you for investigating the avenues to fix it -- on one hand it
seems to me like the defensive change should reside on the client as that is
what's newer and therefore it's the end which has caused the problem; but on
the other hand
Issue #15669 has been updated by Daniel Pittman.
eric sorenson wrote:
That is a pretty rough error message. It'd be good for the 3.0 agent to be
aware of the earlier servers and error out specifically.
In general, we want to add content negotiation to agent-master communication
in 3.x ;
Issue #15669 has been updated by eric sorenson.
Target version changed from 2.7.x to 3.0.0
Keywords set to errors
That is a pretty rough error message. It'd be good for the 3.0 agent to be
aware of the earlier servers and error out specifically.
In general, we want to add content negotiation
Issue #15669 has been updated by eric sorenson.
To be clear though, implementing #6879 should not block investigating and doing
what we can in 3.0.0 for this message specifically.
Feature #15669: A more helpful error message when the puppet master is at
Issue #15669 has been updated by Randall Hansen.
+1. This is unhelpful and we should fix it.
Feature #15669: A more helpful error message when the puppet master is at the
wrong version (2.7.x to 3.0)
Issue #15669 has been updated by Ben Hughes.
Description updated
Feature #15669: A more helpful error message when the puppet master is at the
wrong version (2.7.x to 3.0)
https://projects.puppetlabs.com/issues/15669#change-67582
Author: Ben Hughes
11 matches
Mail list logo
