红帽全球峰会此内容没有您所选择的语言版本。
Chapter 4. Upgrading Puppet
Red Hat Satellite 6.4 only supports Puppet 5. The migration path for Puppet 5 supports only Puppet 4 to Puppet 5 migrations. Therefore, if you are using a version of Puppet prior to version 4, you must upgrade to Puppet 4 prior to upgrading to Satellite 6.4. Satellite 6.3 includes an upgrade path to Puppet 4, for more information, see the Upgrading Puppet section in the Satellite 6.3 Upgrading and Updating Red Hat Satellite guide.
During the Satellite upgrade process, Puppet is upgraded from Puppet 4 to Puppet 5. It is not a separate process. This chapter describes the process of preparing for the upgrade from Puppet 4 to Puppet 5.
Red Hat Satellite and Capsules do not have to be upgraded at the same time. You have the flexibility to upgrade Capsules depending on your progress with testing and upgrading Puppet modules. An alternative is to install new Capsules and move hosts to them after testing. You can use Satellite web UI, the Hammer CLI, or the bootstrap script to move hosts from a Puppet 4 Capsule to a Puppet 5 Capsule.
Cloning an existing Capsule to use for final testing of upgraded Puppet modules is also recommended. Cloning an existing Capsule can take a long time depending on the size of the repositories.
4.1. Configuring Puppet Host Parameters
By default, Satellite 6.4 sets the global parameter enable-puppet5. Provisioning templates, such as Kickstart files, use enable-puppet5 to provision new hosts to use the Puppet 5 agent if available. However, if the Puppet 4 agent is in a Content View attached to a host, this will be used in place of Puppet 5. If you want hosts to use Puppet 5, you must update Content Views associated with the hosts to contain the Puppet 5 agent.
Removing Puppet 4 Host Parameter
If you set the parameter enable-puppet4 in Satellite 6.3, it can now be safely removed.
- In the web UI, navigate to Configure > Host Groups and select the name of the host group you want to configure.
-
Click the Parameters tab, and in the Host Group Parameters area, locate
enable-puppet4. - In the Actions column, click Remove.
- Click Submit to save the changes.
For CLI Users
Remove the enable-puppet4 parameter for all hosts in a hostgroup:
hammer hostgroup delete-parameter \ --hostgroup my_hostgroup \ --name enable-puppet4
# hammer hostgroup delete-parameter \
--hostgroup my_hostgroup \
--name enable-puppet44.2. Testing Puppet Modules
Before upgrading to Satellite 6.4, you must first review your Puppet modules, and make changes, to ensure they are compatible with Puppet 5. For information on the changes in Puppet 5, see the Puppet 5.0 Release Notes on the Puppet website.
Use the Puppet 5.0 Release Notes on the Puppet website and the following guidelines to test your Puppet modules before you begin upgrading:
- Test Puppet modules first on a workstation, separate from Satellite.
-
Check the command syntax using the
puppet parser validatecommand. -
Check for capital letters in the name of a class reference because this is no longer supported. Change class names to lower case; for example, change
Class[MyClass]toClass[myclass]. -
If you have custom version comparison code in Ruby, note that the
Range#intersectioncode to handle SemVer range matches has been removed. -
If you have custom Ruby code that makes use of the deprecated string formatting methods in the
TypeCalculatorclass, change your code to use the replacementTypeFormatterclass because the string formatting methods in theTypeCalculatorhave been removed. For more information, see the Type mismatch describer should expand aliases issue on the Puppet website. -
Previously, if a class was defined more than once their bodies were merged. A warning or error was displayed depending on the status of the
--strictflag. Now, an error is always displayed except for the top scope class indicated by‘’(also known as‘main’).
4.3. Upgrading Satellite Hosts to Puppet 5
Use this section to upgrade Satellite hosts to Puppet 5. Satellite Server and Capsule Server are upgraded to Puppet 5 as part of their respective upgrade procedures.
Prerequisites
- Ensure you complete the upgrade to Satellite 6.4 for Satellite Server. For more information, see Section 3.1, “Upgrading Satellite Server”.
- Ensure you complete the upgrade for the Capsule Server with the hosts attached that you want to upgrade. For more information, see Section 3.3, “Upgrading Capsule Servers”.
-
Ensure there is no
enable-puppet4parameter set for the host or host group to override the globalenable-puppet5parameter. For more information, see Section 4.1, “Configuring Puppet Host Parameters”. - Ensure you have reviewed your Puppet modules and upgraded them where required for Puppet 5. For more information, see Section 4.2, “Testing Puppet Modules”.
- Ensure the associated Content Views have been updated to include Puppet 5 agent.
Procedure
To upgrade a host to Puppet 5, complete the following steps:
- In the Satellite web UI, navigate to Hosts > Content Hosts and select the Content Hosts that you want to upgrade.
- From the Select Action list, select Manage Repository Sets.
- From the Repository Sets Management list, select the Red Hat Satellite 6.3 - Puppet 4 (for RHEL 7 Server) (RPMs) check box.
- From the Select Action list, select Override to Disabled.
- Click Yes to confirm the action.
- When the process completes, on the same set of hosts from the previous steps, from the Select Action list, select Manage Packages.
- Click Update All Packages.
- Click Yes to confirm the action.
For CLI Users
On the host, search for the Puppet 4 RPM repository:
subscription-manager repos --list-enabled |grep puppet4
# subscription-manager repos --list-enabled |grep puppet4Copy to Clipboard Copied! Toggle word wrap Toggle overflow Disable the Puppet 4 repository you find on the host, for example:
subscription-manager repos \ --disable=rhel-7-server-satellite-tools-6.3-puppet4-rpms
# subscription-manager repos \ --disable=rhel-7-server-satellite-tools-6.3-puppet4-rpmsCopy to Clipboard Copied! Toggle word wrap Toggle overflow For more information about format of Puppet repositories, see Red Hat Satellite Tools - Puppet 4 in the Red Hat Satellite {PreviousVersion} Release Notes.
Until BZ#1649764 is resolved, update the
goferpackage:yum update gofer
# yum update goferCopy to Clipboard Copied! Toggle word wrap Toggle overflow Restart goferd.
systemctl restart goferd
# systemctl restart goferdCopy to Clipboard Copied! Toggle word wrap Toggle overflow Update all packages:
yum update
# yum updateCopy to Clipboard Copied! Toggle word wrap Toggle overflow
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}