第4章 Post-Upgrade Tasks
Some of the procedures in this section are optional. You can choose to perform only those procedures that are relevant to your installation.
If you use the PXE-based discovery process, then you must complete the discovery upgrade procedure on Satellite and on any Capsule Server with hosts that you want to be listed in Satellite on the Hosts > Discovered hosts page.
4.1. Upgrading Discovery リンクのコピーリンクがクリップボードにコピーされました!
This section describes updating the PXELinux template and the boot image passed to hosts that use PXE booting to register themselves with Satellite Server.
From Satellite 6.4, provisioning templates now have a separate association with a subnet, and do not default to using the TFTP Capsule for that subnet. If you create subnets after the upgrade, you must specifically enable the Satellite or a Capsule to provide a proxy service for discovery templates and then configure all subnets with discovered hosts to use a specific template Capsule.
During the upgrade, for every subnet with a TFTP proxy enabled, the template Capsule is set to be the same as the TFTP Capsule. After the upgrade, check all subnets to verify this was set correctly.
These procedures are not required if you do not use PXE booting of hosts to enable Satellite to discover new hosts.
4.1.1. Upgrading Discovery on Satellite Server リンクのコピーリンクがクリップボードにコピーされました!
Update the Discovery template in the Satellite web UI:
- Navigate to Hosts > Provisioning templates.
-
On the
PXELinux global defaultline, click Clone. -
Enter a new name for the template in the Name field, for example
ACME PXE global default. -
In the template editor field, change the line
ONTIMEOUT localtoONTIMEOUT discoveryand click Submit. - Navigate to Administer > Settings.
-
Locate
Global default PXELinux templateand click on its Value. - Select the name of the newly created template from the menu and click the tick button.
- Navigate to Hosts > Provisioning templates.
- Click Build PXE Default, then click OK.
- In the Satellite web UI, go to Configure > Discovery Rules and associate selected organizations and locations with discovery rules.
4.1.2. Upgrading Discovery on Capsule Servers リンクのコピーリンクがクリップボードにコピーされました!
Verify that the Foreman Discovery package is current on Satellite Server.
satellite-maintain packages install tfm-rubygem-foreman_discovery
# satellite-maintain packages install tfm-rubygem-foreman_discoveryCopy to Clipboard Copied! Toggle word wrap Toggle overflow If an update occurred in the previous step, restart the
satellite-maintainservices.satellite-maintain service restart
# satellite-maintain service restartCopy to Clipboard Copied! Toggle word wrap Toggle overflow Upgrade the Discovery image on the Satellite Capsule that is either connected to the provisioning network with discovered hosts or provides TFTP services for discovered hosts.
satellite-maintain packages install foreman-discovery-image
# satellite-maintain packages install foreman-discovery-imageCopy to Clipboard Copied! Toggle word wrap Toggle overflow On the same instance, install the package which provides the Proxy service, and then restart
foreman-proxyservice.satellite-maintain packages install tfm-rubygem-smart_proxy_discovery service foreman-proxy restart
# satellite-maintain packages install tfm-rubygem-smart_proxy_discovery # service foreman-proxy restartCopy to Clipboard Copied! Toggle word wrap Toggle overflow - In the Satellite web UI, go to Infrastructure > Capsules and verify that the relevant Capsule lists Discovery in the features column. Select Refresh from the Actions drop-down menu if necessary.
Go to Infrastructure > Subnets and for each subnet on which you want to use discovery:
- Click the subnet name.
- On the Capsules tab, ensure the Discovery Capsule is set to a Capsule you configured above.
4.1.3. Verifying Subnets have a Template Capsule リンクのコピーリンクがクリップボードにコピーされました!
Ensure all subnets with discovered hosts have a template Capsule:
- In the Satellite web UI, navigate to Infrastructure > Subnets.
- Select the subnet you want to check.
- On the Capsules tab, ensure a Template Capsule has been set for this subnet.
For more information about configuring subnets with template Capsules, see Configuring Discovery Subnets in the Red Hat Satellite Managing Hosts guide.