Managing Red Hat Enterprise Linux Clients
The following sections provide guidance on managing Red Hat Expanded Support clients, this includes Salt clients and traditional systems.
This section provides guidance on server configuration for Red Hat Enterprise Linux Channels provided by SUSE.
Minimum of 8 GB RAM and at least two physical or virtual CPUs. Taskomatic will use one of these CPUs.
Taskomatic requires of minimum of 3072 MB RAM. This should be set in
Provision enough disk space.
/var/spacewalkcontains all mirrored RPMs. For example, Red Hat Enterprise Linux 6 x86_64 channels require 90 GB and more.
LVM or an NFS mount is recommended.
Access to RHEL 5/6/7 Subscription Media.
Access to RHEL Media or Repositories
Access to Red Hat base media repositories and RHEL installation media is the responsibility of the user. Ensure that all your RHEL systems obtain support from RHEL or all your RHEL systems obtain support from SUSE. If you do not follow these practices you may violate terms with Red Hat.
This section provides tips on Red Hat Enterprise Linux channel management.
The base parent distribution Red Hat Enterprise Linux channel per architecture contains zero packages. No base media is provided by SUSE. The RHEL media or installation ISOs should be added as child channels of the Red Hat Enterprise Linux parent channel.
The Red Hat Enterprise Linux and tools channels are provided by SUSE Customer Center (SCC) using
It can take up to 24 hours for an initial channel synchronization to complete.
When you have completed the initial synchronization process of any Red Hat Enterprise Linux channel it is recommended to clone the channel before working with it. This provides you with a backup of the original synchronization.
The following procedure guides you through setup of the RHEL media as a Uyuni channel. All packages on the RHEL media will be mirrored into a child channel located under RES 5/6/7 distribution per architecture.
Create a new Channel by log in to the Web UI and selecting.
Fill in basic channel details and add the channel as a child to the corresponding RES 5/6/7 distribution channel per architecture from SCC. The base parent channel should contain zero packages.
Modify the RES 5/6/7 activation key to include this new child channel.
As root on the Uyuni command line copy the ISO to the
Create a directory to contain the media content:
mkdir -p /srv/www/htdocs/pub/rhel
Mount the ISO:
mount -o loop /tmp/name_of_iso /srv/www/htdocs/pub/rhel
spacewalk-repo-syncto synchronize Red Hat Enterprise Linux 7 packages:
spacewalk-repo-sync -c channel_name -u https://127.0.0.1/pub/rhel/ Repo URL: https://127.0.0.1/pub/rhel/ Packages in repo: [...] Packages already synced: [...] Packages to sync: [...] [...]
To synchronize RES 5/6 packages:
spacewalk-repo-sync -c channel_name -u https://127.0.0.1/pub/rhel/Server/ Repo URL: https://127.0.0.1/pub/rhel/Server/ Packages in repo: [...] Packages already synced: [...] Packages to sync: [...] [...]
When the channel has completed the synchronization process you can use the channel as any normal Uyuni channel.
Attempting to synchronize the repository will sometimes fail with this error:
[Errno 256] No more mirrors to try.
To troubleshoot this error, look at the HTTP protocol to determine if
spacewalk-repo-sync is running:
Start debugging mode with
Check the output of
/usr/bin/spacewalk-repo-sync --channel <channel-label> --type yum
If you want to disable debug mode, use
This section will guide you through registering RHEL clients with Uyuni.
This section assumes you have updated your server to the latest patch level.
Ensure you have the corresponding Red Hat Enterprise Linux product enabled and required channels have been fully synchronized:
Product: Red Hat Enterprise Linux 7
Product: Red Hat Enterprise Linux 6
Checking Synchronization Progress
To check if a channel has finished synchronizing you can do one of the following:
Create an activation key associated with the Red Hat Enterprise Linux channel.
The following procedure demonstrate creating a bootstrap repository for RHEL:
On the server command line as root, create a bootstrap repo for RHEL with the following command:
If you use a dedicated channel per RHEL version, specify it with the
cp bootstrap.sh res7-bootstrap.sh
The following procedure will guide you through registering a Salt client using the bootstrap script.
For your new client download the bootstrap script from the Uyuni server:
wget --no-check-certificate https://`server`/pub/bootstrap/res7-bootstrap.sh
Add the appropriate res-gpg-pubkey--.key to the
ORG_GPG_KEYkey parameter, comma delimited in your
res7-bootstrap.shscript. These are located on your Uyuni server at:
res7-bootstrap.shscript executable and run it. This will install necessary Salt packages from the bootstrap repository and start the Salt client service:
chmod +x res7-bootstrap.sh ./res7-boostrap.sh
From the Uyuni Web UI selectand accept the new client’s key.
If bootstrapping a client fails it is usually caused by missing packages. These missing packages are contained on the RHEL installation media. The RHEL installation media should be loop mounted and added as a child channel to the Red Hat Enterprise Linux channel. See the warning in [bp.expanded-support.resclients] on access to RHEL Media.
The following procedure will guide you through the registration of a Salt client manually.
Add the bootstrap repository:
yum-config-manager --add-repo https://`server`/pub/repositories/res/7/bootstrap
Install the salt-minion package:
yum install salt-minion
Edit the Salt client configuration file to point to the Uyuni server:
mkdir /etc/salt/minion.d echo "master:`server_fqdn`" > /etc/salt/minion.d/susemanager.conf
Start the client service:
systemctl start salt-minion
From the Uyuni Web UI select theand accept the new client’s key.