Hi, 'foreman-installer --upgrade-puppet' will take care of most of the things that are listed in foreman wiki. There are just some additional parameters that need to be changed.
For the workflow: I ran --upgrade-puppet and afterwards I ran foreman-installer again to reset answers to their "new" settings or change some that --upgrade-puppet didn't change. I'm not sure if my list is complete but it was sufficient for my foreman/katello usage. My full workflow was something along these lines (including katello update from 3.1 to 3.2) #https://projects.theforeman.org/issues/17639 mkdir /var/lib/tftpboot/grub2 mkdir /var/lib/tftpboot/grub chown -R foreman-proxy:foreman-proxy /var/lib/tftpboot foreman-installer -v --scenario katello --upgrade vim /usr/share/katello-installer-base/hooks/pre/31-upgrade-puppet.rb # --> add puppet-agent-oauth or https://github.com/Katello/katello-installer/pull/467 vim /usr/share/katello-installer-base/modules/certs/manifests/candlepin.pp # http://projects.theforeman.org/issues/18129 rm /usr/share/katello-installer-base/hooks/pre/29-remove_package_httpd_conf.rb /usr/share/katello-installer-base/hooks/post/29-create_package_httpd_conf.rb # http://projects.theforeman.org/issues/18132 foreman-installer --upgrade-puppet systemctl stop puppetserver /usr/sbin/usermod -d /opt/puppetlabs/server/data/puppetserver puppet systemctl start puppetserver foreman-installer -v --scenario katello \ --reset-foreman-proxy-puppetdir \ --reset-foreman-proxy-puppetrun-cmd \ --reset-foreman-proxy-puppetca-cmd \ --reset-foreman-proxy-plugin-pulp-puppet-content-dir \ --reset-foreman-puppet-home \ --reset-foreman-puppet-ssldir \ --reset-foreman-proxy-puppet-ssl-ca \ --reset-foreman-proxy-puppet-ssl-cert \ --reset-foreman-proxy-puppet-ssl-key \ --foreman-proxy-puppetssh-command "/opt/puppetlabs/bin/puppet agent --onetime --no-usecacheonfailure --no-daemonize --no-splay" \ --foreman-proxy-ssldir /etc/puppetlabs/puppet/ssl I use theforeman-puppet for my configuration. After the puppet4 upgrade I had to add those additional parameters for my foreman server: server_foreman_ssl_ca: "/etc/puppetlabs/puppet/ssl/ssl_ca.pem" server_foreman_ssl_cert: "/etc/puppetlabs/puppet/ssl/client_cert.pem" server_foreman_ssl_key: "/etc/puppetlabs/puppet/ssl/client_key.pem" For my puppet capsules I chose not to upgrade them, I rather reinstalled them. I did run into more issues there but thats because I run pulp/puppet on different capsules rather than both on one capsule: http://projects.theforeman.org/issues/17605 http://projects.theforeman.org/issues/18185 http://projects.theforeman.org/issues/18182 The pulp capsules just work after I applied http://projects.theforeman.org/issues/17605 foreman-installer --scenario capsule --upgrade --capsule-certs-tar certs.tar --certs-update-all --certs-regenerate true --certs-deploy true I think thats all :) Greetings Klaas Demter ATIX - The Linux & Open Source Company www.atix.de ----- Ursprüngliche Mail ----- Von: "Lachlan Musicman" <[email protected]> An: [email protected] Gesendet: Donnerstag, 16. Februar 2017 03:54:31 Betreff: Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails Klaas, Thank you for this, much appreciated. We have decided to revert back to snapshot taken last week and try again - your notes will be very helpful. One thing in particular that has us confused is 18131 "foreman-installer --upgrade-puppet fails to set new paths for foreman-installer" http://projects.theforeman.org/issues/18131 In particular a full workflow. ie, after running foreman-installer --upgrade-puppet you ran the listed solution in your comment? I read the details on the Foreman/Puppet upgrade page, which was interesting for background: http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4 and it includes a similar, but not the same, step. I presumed that the upgrade instructions listed on the Katello 3.2 page would list any extra steps that might need to be taken. I'll report back/take notes on how I go. Cheers L. ------ The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 15 February 2017 at 19:41, Klaas Demter <[email protected]> wrote: > Hey, > I've successfully upgraded to puppet4 on my katello. In the process I've > fixed, reported and worked around several issues. Feel free to check the > PRs/discussions of these tickets: > http://projects.theforeman.org/issues/18123 > http://projects.theforeman.org/issues/18129 > http://projects.theforeman.org/issues/18131 > http://projects.theforeman.org/issues/18132 > > After those workaround/fixes the upgrade katello 3.1.x to 3.2.3 worked for > me including the puppet4 upgrade > > > if you encounter different issues create a bugreport and maybe even try to > fix it and create a pull request :) > > Greetings > Klaas Demter > > ATIX - The Linux & Open Source Company > www.atix.de > > ----- Ursprüngliche Mail ----- > Von: "Mario Gamboa" <[email protected]> > An: "Foreman users" <[email protected]> > Gesendet: Mittwoch, 15. Februar 2017 09:18:54 > Betreff: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails > > Any solution ? > > Same issues here the thing that is amazing the katello and foreman team > they are planning to no support anymore puppet 3 on 1.15 foreman but how we > are going to upgrade our current puppet 3 to 4 is ridiculous > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
