You're correct John - Puppet 4 masters using Puppet Server will work with Puppet 3 agents. If the catalog compiles (Henrik's point), the agent/master comms will be fine.
Note the same is not true for Apache/Passenger based Puppet 4 setups - the URL rewriting that enables the compatibility is only implemented in puppetserver. --eric On Tuesday, January 15, 2019 at 5:52:35 AM UTC-8, jcbollinger wrote: > > > > On Monday, January 14, 2019 at 10:01:21 AM UTC-6, Henrik Lindberg wrote: >> >> On 2019-01-14 16:22, Peter Berghold wrote: >> > I am about to have our first Puppet 4 Puppet master into our production >> > environment. We have a very large community of Puppet 3 "leaf nodes" >> > being managed by our old Puppet 3 infrastructure. >> > >> > What issues might I run into with that and what should I do to mitigate >> > this? >> > >> >> It is a quite open ended question unfortunately. You may want to start >> reading here: https://puppet.com/docs/puppet/4.10/upgrade_major_pre.html >> and then come back with more specific questions. >> > > > Hmmm. I took the question to be about whether there were known issues > revolving around a P4 master serving catalogs to P3 agents. I didn't think > P4 broke the pattern that the master supports agents from the previous > generation. Or is that less of a pattern than I thought? > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ece3301a-9651-4238-a02c-3ded8831ad1b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
