Since you did not provide an “expected outcome” I assume from the style of your post that you do not use Puppet and thus do not want to install it.
For the installation snippet to become active, you need to either have a puppetserver set on your host or have the host parameter “force-puppet” set and evaluationg to true, so those are the places I would look first.
Hi! We use puppet and puppetserver on Foreman (Openvox realy). The problem is that the registration script is trying to install the puppet package, and the package is called puppet-agent (openvox-agent).
Foreman web-ui Hosts→Register Host.
End of registration script Foreman 3.15:
```
Restart yggdrasild if installed and running
End of registration script Foreman 3.17:
```
bash /root/registration_host_init.sh
init_conf_status=$?
if [ $init_conf_status -ne 0 ]; then
echo “Host initialization script failed, see the logs for more information.”
echo “You can access the script source by running ‘cat /root/registration_host_init.sh’”
cleanup_and_exit $init_conf_status
fi
`` In 3.16 or 3.17 I see bash /root/registration_host_init.sh and in /root/registration_host_init.sh I see:
`` dnf -y install puppet yum -t -y install puppet
```
Script fails with errors:
Error:
Problem: conflicting requests
nothing provides augeas-libs >= 1.10.1 needed by puppet-7.27.0-1.el9.noarch from rbru-epel-9
nothing provides augeas >= 1.10.1 needed by puppet-7.27.0-1.el9.noarch from rbru-epel-9
nothing provides /usr/bin/ruby needed by puppet-7.27.0-1.el9.noarch from rbru-epel-9
nothing provides ruby(selinux) needed by puppet-7.27.0-1.el9.noarch from rbru-epel-9
If you want to skip the Puppet/OpenVox setup during registration completely and handle installation and setup yourself, you can set the skip-puppet-setup parameter (either per-host, per-hostgroup or as a global parameter, whatever fits your needs).