Switching to openvox on foreman server/proxies

Support
1

Problem:
Today, I wanted to switch to openvox after upgrading my foreman server and proxies to 3.19/4.21. Installation docs suggest that it should be enough to switch from the puppet to the openvox repository. Did that and updated to latest openvox-server and agent. However, running foreman-installer afterwards results in an error:

2026-09-10 20:35:55 [ERROR ] [configure] Execution of '/bin/dnf -y install puppetserver' returned 1: Updating Subscription Management repositories.
2026-09-10 20:35:55 [ERROR ] [configure] subscription-manager plugin disabled 0 system repositories with respect of configuration in /etc/dnf/plugins/subscription-manager.conf

Is there a migration document with guidelines for the migration from puppetserver to openvox-server?

Expected outcome:
Configuring the system for openvox server

Foreman and Proxy versions:
3.19.1 4.21.1

Distribution and version:
AlmaLinux 9.8

2

We recently did that migration and we did the following:

# Remove Perforce Puppet Repos (depending on your setup)
# Add OpenVox Repos (depending on your setup)
dnf clean all && dnf makecache
dnf update -y
foreman-installer --puppet-server-package openvox-server --puppet-client-package openvox-agent

That worked for us on 3.16 though I can not find where this might be documented.

3

Thanks. Strange that it has the package names set in the answers file although I have never touched them (I think).

The alternative to setting the package names is to reset the setting, which reverts back to the default which is openvox (at least for 3.19).

foreman-installer --reset-puppet-server-package --reset-puppet-client-package

Then it runs through just fine. Although it didn’t even complain about the client package. It seems to check something else there to find out whether the puppet/openvox agent is installed/running or not…