How to install Red Hat Update Infrastructure on an existing OpenStack instance
Red Hat Update Infrastructure (RHUI) enables automatic updates to our Red Hat customers, providing benefits such as the reliable availability of patch updates and Red Hat approved OS templates.
This article provides advice on how to update your existing Red Hat instances (virtual machines) to target UKCloud's approved RHUI.
There are two prerequisites for performing this operation:
The host can resolve to the RHUI DNS records (contact Customer Support for the IP addresses and domain names for these records). You can achieve this by configuring an A record on your local DNS or configuring an
/etc/hostsfile with the appropriate information. For internet connectivity, the required domain name is in public DNS.
All hosts using the service must be able to access the local RHUI server on port 443 (HTTPS). Ensure that the configured Security Groups allow outbound connectivity on port 443. If you have any questions on this, contact UKCloud Support.
You can find the installer RPM files in an ISO image. Before you can mount this to an existing instance, you'll need to create a volume from the image.
In the Horizon Web UI, locate the image
UKCloud-RHUI-Standard-Assured.iso, click the action button and select Create Volume.
Use the default settings presented by the dialog to copy the ISO to a 1GB Tier 2 volume, and click Create Volume.
Locate the Red Hat instance where you want to install RHUI support and select Attach Volume.
Select the newly created volume and then click Attach Volume.
Select the instance name and check at the bottom of the Instance Overview to see that the volume is attached, and what its device name is.
As root, mount the volume inside the VM, using the device name from step 5.
Install the relevant RPM.
For example, for RHEL7:
rpm -ivh IL2-Client-RHEL7-Standard-2.0-1.noarch.rpm.
yum clean all
Test the RHUI is working:
The first time you update from RHUI you may be prompted to accept the following two certificates:
The Red Hat entitlement certificate
The Client entitlement certificate
The primary issues you may encounter are:
Check the DNS lookup is working and you have the correct entry for Assured.
443 not accessible
Check your firewall configuration, including local firewalls (iptables) and security groups applied to instances.
Ensure you have the correct destination IP entry.
Ensure you have installed the correct RPM for your release.
If you find a problem with this article, click Improve this Doc to make the change yourself or raise an issue in GitHub. If you have an idea for how we could improve any of our services, send an email to firstname.lastname@example.org.