| Summary: | [RFE] Need to automate the manual steps required to upgrade the client. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Giridhar <gkonda> | ||||
| Component: | Puppet | Assignee: | satellite6-bugs <satellite6-bugs> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Peter Ondrejka <pondrejk> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.3.0 | CC: | andrew.schofield, arahaman, bkearney, brian.millett, bruce.howells, ccrisafu, cdonnell, daniele, ehelms, fgarciad, gpulido, inecas, jalviso, ktordeur, lpramuk, michiel.smit, mlesieur, msecaur, nshaik, oprazak, rajgupta, rbertolj, riehecky, satellite6-bugs, smercurio, sthirugn, swadeley, vdeshpan, vvasilev | ||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature, UserExperience | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-11-22 17:51:49 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1547951 | ||||||
| Attachments: |
|
||||||
|
Description
Giridhar
2017-11-27 06:12:45 UTC
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. Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you. |