Problem Statement

Currently, foreman-maintain does not include virt-who configuration files in Satellite backup. The virt-who configuration files are not included in 'config_files.tar.gz' in Satellite backup:

# tar tvf config_files.tar.gz | grep -i virt
-rw-r--r-- root/root         0 2017-09-11 14:05 etc/foreman-installer/applied_hooks/post/set_virt_who_on_pools
-rw-r--r-- root/root            52 2024-01-09 17:12 etc/hammer/cli.modules.d/foreman_virt_who_configure.yml
hrw-r--r-- root/root                   0 2017-09-11 14:05 etc/foreman-installer/applied_hooks/post/set_virt_who_on_pools link to etc/foreman-installer/applied_hooks/post/set_virt_who_on_pools
-rw-r----- root/foreman-proxy        214 2025-03-12 12:27 etc/foreman-proxy/settings.d/dhcp_libvirt.yml
-rw-r----- root/foreman-proxy        213 2025-03-12 12:27 etc/foreman-proxy/settings.d/dns_libvirt.yml 

When this backup is used with satellite-clone to migrate Satellite server from RHEL 8 to RHEL 9, the cloned Satellite server lacks the virt-who configuration that existed on the source RHEL 8 Satellite server.

User Experience & Workflow

[Describe the experience/interaction/steps of this request as a workflow
with expected outcomes at each step. What is the end-state and how will
they be able to verify a successful outcome?]

Without virt-who configurations not included in Satellite backup, users using this backup with satellite-clone will have to manually install virt-who on the target Satellite server, and reconfigure virt-who.

Out of the context of using satellite-clone with the backup, if the virt-who configurations are lost from the Satellite server (either intentionally or unintentionally), the users have to manually reconfigure them.

Requirements
Implement a mechanism in satellite-maintain to do the following: * Detect if virt-who is enabled or not on the Satellite server being backed up.

• If yes, include the relevant virt-who configurations in the backup.
• During restore on the target Satellite server, check if virt-who is installed or not. If not, install it, restore the configurations , then restart virt-who service.

Business Impact

Users of satellite-clone expect a successful end-to-end cloning of their Satellite server when they migrate across RHEL releases. If this feature is not implemented, users will have to manually install virt-who on the target Satellite server, and reconfigure virt-who.

Moreover, out of the context of using satellite-clone with the backup, having virt-who configurations included in the backup supports fast recovery of functionality in case a restoration is needed.