Red Hat Bugzilla – Bug 1517624
[RFE] Need to automate the manual steps required to upgrade the client.
Last modified: 2018-11-02 01:44:42 EDT
Description of problem: Need to automate the manual steps required to upgrade the client. Version-Release number of selected component (if applicable): Satellite 6.3.0 Puppet: 4.10.7 How reproducible: 100% Steps to Reproduce: 1.In order to upgrade the puppet client in satellite 6.3.0 below steps needs to be performed manually 2. Move the ssl directory # mv /var/lib/puppet/ssl /etc/puppetlabs/puppet/ssl 3. Edit the /etc/puppetlabs/puppet.conf and set the master entries manually # vi /etc/puppetlabs/puppet/puppet.conf Actual results: The above steps need to be performed manually Expected results:The above steps should be automated Additional info: Either the package needs to be modified in such a way that a script is included to automate the manual steps or a package that automates the above steps and this should be installed as dependency to puppet-agent.
Created redmine issue http://projects.theforeman.org/issues/22400 from this bug
Hello see comment https://bugzilla.redhat.com/show_bug.cgi?id=1547951#c17
This reminds me of rejected RFE, see https://bugzilla.redhat.com/show_bug.cgi?id=1511505 So simply you can create your own script to be executed on remote hosts to migrate them on puppet4: --8<------------------ subscription-manager repos --enable rhel-7-server-satellite-tools-6.3-puppet4-rpms yum -y upgrade cp -fp /etc/puppet/puppet.conf.rpmsave /etc/puppetlabs/puppet/puppet.conf cp -rfp /var/lib/puppet/ssl /etc/puppetlabs/puppet sed -i 's|vardir\s*=.*|vardir = /opt/puppetlabs/puppet/cache|' /etc/puppetlabs/puppet/puppet.conf sed -i 's|logdir\s*=.*|logdir = /var/log/puppetlabs/puppet|' /etc/puppetlabs/puppet/puppet.conf sed -i 's|rundir\s*=.*|rundir = /var/run/puppetlabs|' /etc/puppetlabs/puppet/puppet.conf sed -i 's|ssldir\s*=.*|ssldir = /etc/puppetlabs/puppet/ssl|' /etc/puppetlabs/puppet/puppet.conf service puppet restart ---8<------------------
Created attachment 1454206 [details] new job template to update puppet and katello agent I think that just adding a new template like this will be a good solution to this and make migrations easier. It does both puppet 3 to 4 and katello at once but they can easily be extended to do things like update puppet only if enable-puppet4 is true, etc if needed.
I added a quick job template I created to handle my puppet/katello updates. This is something that should be safe to have run on all hosts once a day until all the migrations were completed.