Last Modified: 2021-04-27 06:31:02 UTC
Cheat sheet for various Red Hat Satellite tasks from a newbie to a newbie.
up to Satellite 6.7 RHEL 7.X
4 CPU Cores
20 GB of RAM
300 GB disk space
for more info see the prerequistes guide
Satellite up to version 6.7 uses puppet for installation. You can use
to restore files modified by puppet.
Satellite requires the Red Hat Satellite Infrastructure Subscription, check if it’s available with
subscription-manager list --all --available --matches 'Red Hat Satellite Infrastructure Subscription'
If not attach it with
subscription-manager attach --pool=pool_id
Next disable all repos and enable only supported repostories via
subscription-manager repos --disable "*"
and enable required repositories
subscription-manager repos --enable=rhel-7-server-rpms \ --enable=rhel-7-server-satellite-6.6-rpms \ --enable=rhel-7-server-satellite-maintenance-6-rpms \ --enable=rhel-server-rhscl-7-rpms \ --enable=rhel-7-server-ansible-2.8-rpms
then clean cached all repo data via
yum clean all
and install satellite packages via
yum install satellite
Install satellite with
satellite-installer --scenario satellite \ --foreman-initial-organization "initial_organization_name" \ --foreman-initial-location "initial_location_name" \ --foreman-initial-admin-username admin_user_name \ --foreman-initial-admin-password admin_password
satellite-maintain for doing offline and online backups
satellite-maintain backup offline /backup/
when using the online option make sure that no new content view or content view versions should be created while the backup is running. basically satellite should be idle.
The online/offline options also backup /var/lib/pulp, which contains all downloaded packages. This could be huge. There’s an option to skip this so
satellite-maintain backup offline --skip-pulp-tar /backup/
|For a restore you always need the content of /var/lib/pulp.|
This is mainly usefull for cloning satellite. You backup everything except /var/lib/pulp, copy the backup to a second system and rsync /var/lib/pulp to the new system. Then restore the backup and satellite should work as normal on the clone.
Satellite also supports backups via LVM snapshots. For more information see Snapshot backup
Read the Satellite release notes
Do a offline backup see [Backup / Restore]
You could clone satellite to a other system
If there are local changes to dhcpd or dns configurations use
satellite-installer --foreman-proxy-dns-managed=false --foreman-proxy-dhcp-managed=false
to stop satellite-install from overwriting those files.
install the latest version of satellite-maintain via
yum install rubygem-foreman_maintain
check for available satellite versions with
satellite-maintain upgrade list-versions
test the possible upgrade with
satellite-maintain upgrade check --target-version 6.7
and finally run the upgrade and PRAY!
satellite-maintain upgrade run --target-version 6.7
Satellite installs a yum plugin called
foreman-protector. If you try
to install a package via yum you get the following message
WARNING: Excluding 12190 packages due to foreman-protector. Use foreman-maintain packages install/update <package> to safely install packages without restrictions. Use foreman-maintain upgrade run for full upgrade.
satellite-maintain install <package name>
This should be done via satellite-maintain because all packages are locked by default (see Installing packages via yum).
This basically comes down to running
oreman-maintain upgrade run --target-version 6.6.z
for upgrading OS packages if you have satellite 6.6 installed.