We ran into a couple issues, all on centos6. Several package conflicts. Had to remove the puppetlabs-release package to get the puppetlabs-release-pc1 package to install. New puppetserver package didn't obsolete the old puppet-server package, had to uninstall puppet-server package first. puppetdb-termini package doesn't appear to obsolete puppetdb-terminus package. These might have been fixed in the meantime.
If you're using mcollective-puppet, mcollective-puppet-agent can't find puppet at new path, needed to add "plugin.puppet.command = /opt/puppetlabs/bin/puppet agent" to the server.cfg on all mcollective servers. The puppetdb upgrade was fairly painless. Though, the fact that they dropped the v2 and v3 apis and completely altered the v4 api, as compared to the v4-experimental api, so that essentially no existing tools could work with the new puppetdb seems pretty boneheaded. What's the point of having an api if you drop it out the window? Other than that, there were a few differences between the future parser in 3.8 and the actual implementation in 4, but nothing to difficult to fix. On Monday, August 24, 2015 at 1:00:30 PM UTC-7, Christopher Wood wrote: > > I am not seeing a large amount of blog entries complaining about this > upgrade, how has that gone for you? Is there anything you found > particularly painful? Would you have done anything different in retrospect? > > I'm staring down a 3.7.2 -> 4.2.1 upgrade and after reading a number of > docs the back-of-the-envelope optimal upgrade path is as follows. If any of > you have commentary I am quite interested, otherwise I will try it and see > what happens. I feel like this might be more time-consuming work but less > brainpower effort than just yanking everything to 4.2. > > 1) rpms up to puppet 3.8 > > PostgreSQL 8.4 to 9.4 > PuppetDB 2.2.2 to 2.3.7 > (puppetdb-terminus from 2.2.2 to 2.3.7) > Puppet 3.7.2 to 3.8.2 > > 2) enable the future parser > > 3) replace puppet 3.8.2, passenger 5 with puppetserver 1.1.1 > > 4) replace puppetserver 1.1.1 with puppetserver 2.1.1 > > 5) upgrade PuppetDB from 2.3.7 to 3.0.2 > > 6) use the puppetlabs-puppet_agent forge module to upgrade agents to 4.2.1 > > > My reading: > > https://docs.puppetlabs.com/puppet/latest/reference/ > > https://docs.puppetlabs.com/puppet/4.2/reference/upgrade_major_pre.html > https://docs.puppetlabs.com/puppet/4.2/reference/upgrade_major_server.html > https://docs.puppetlabs.com/puppet/4.2/reference/upgrade_major_agent.html > https://docs.puppetlabs.com/puppet/4.2/reference/upgrade_major_post.html > > https://forge.puppetlabs.com/puppetlabs/puppet_agent > > https://docs.puppetlabs.com/puppetdb/2.3/upgrade.html > > http://docs.puppetlabs.com/puppetdb/3.0/upgrade.html > > http://www.postgresql.org/docs/9.4/static/upgrading.html > > (Although I may dump/restore the data via puppetdb since that's the actual > api to the data, we do not log in via PostgreSQL.) > -- 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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b21eff5b-49b4-4e98-8385-7850a96d0fa0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
