Procedure 8.6. How to Upgrade the Discovery Feature of Satellite 6

1. Verify that all relevant packages are up-to-date on the Satellite server:

   # yum upgrade ruby193-rubygem-foreman_discovery

   Restart the Satellite server if any packages were updated.
2. 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.

   # yum upgrade foreman-discovery-image

3. On the same instance, install the package which provides the Proxy service, and then restart foreman-proxy service. Discovered hosts in Satellite 6.1 are no longer required to have direct connection to Satellite Server.

   # yum install rubygem-smart_proxy_discovery
   # service foreman-proxy restart
   

4. All subnets with discovered nodes need this specified in Satellite Server so it connects via the Foreman Proxy. In the web UI, navigate to Infrastructure → Capsules and verify that the desired proxy lists the Discovery feature. If it does not, click Refresh features.
5. Navigate to Infrastructure → Subnets and select the required Smart Proxy for each subnet that you want to use discovery, and verify that it is connected to the Discovery Proxy.
6. Navigate to Provisioning Templates, edit the PXELinux global default template and modify it according to the example below.

   Note

   Different options appear on the APPEND line compared to the Satellite 6.0 release.

   LABEL discovery
   MENU LABEL Satellite 6 Discovery
   MENU DEFAULT
   KERNEL boot/fdi-image-rhel_7-vmlinuz
   APPEND initrd=boot/fdi-image-rhel_7-img rootflags=loop root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset proxy.url=https://SATELLITE_CAPSULE_URL:9090 proxy.type=proxy
   IPAPPEND 2
   

   The proxy.type option can be either proxy or foreman. If you specify proxy then all communication goes through the Satellite Capsule. This is the preferred method. If you specify foreman then all communication goes directly to the Satellite Server. This is the method used by Satellite 6.0.

   Note

   When using proxy type, the default port on Satellite Capsule is 9090, but for direct communication with Satellite Server, you need to use port 80.
   The proxy.url option specifies the URL of the Satellite Capsule or Server depending on the previous setting. Both HTTP and HTTPS schemes are supported.
   It is possible to omit the proxy.url option to determine the Capsule DNS name from its SRV record. This might be useful when there are multiple discovery subnets. Review the global settings and permissions in the Satellite Server user interface. See the Red Hat Satellite 6.1 User Guide for more information.