Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1517624 - [RFE] Need to automate the manual steps required to upgrade the client.
Summary: [RFE] Need to automate the manual steps required to upgrade the client.
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Puppet
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high with 3 votes vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
Depends On:
Blocks: 1547951
TreeView+ depends on / blocked
Reported: 2017-11-27 06:12 UTC by Giridhar
Modified: 2019-03-29 03:42 UTC (History)
27 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
new job template to update puppet and katello agent (deleted)
2018-06-24 21:40 UTC, Steven Mercurio
smercurio: review+

System ID Priority Status Summary Last Updated
Foreman Issue Tracker 22400 None None None 2018-01-24 09:58:25 UTC
Red Hat Bugzilla 1547951 None NEW Updating puppet agent from v3 to v4 doesnot migrate the configuration 2019-04-07 23:11:03 UTC
Red Hat Knowledge Base (Solution) 3375371 None None None 2018-03-08 09:38:26 UTC

Internal Links: 1547951

Description Giridhar 2017-11-27 06:12:45 UTC
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:


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.

Comment 3 Ondřej Pražák 2018-01-24 09:58:23 UTC
Created redmine issue from this bug

Comment 5 Stephen Wadeley 2018-04-26 08:24:03 UTC

see comment

Comment 7 Lukas Pramuk 2018-05-16 15:25:12 UTC
This reminds me of rejected RFE, see

So simply you can create your own script to be executed on remote hosts to migrate them on puppet4:
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

Comment 8 Steven Mercurio 2018-06-24 21:40:55 UTC
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.

Comment 9 Steven Mercurio 2018-06-24 21:42:51 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.