Archy's Blog

  NOTE: this guide exists for Upgrading from v3.5 to v3.6 as well -->  here With the current version, the  official documentation  is quite good and can be referenced. I would recommend executing all of these commands in a tmux session so that your session will remain on the server in case anything happens to your workstation. Start by checking for running tasks that would prohibit an update: [root@katello01 ~]# foreman-rake katello:upgrade_check Next, update the katello host and reboot if yum tells you to: [root@katello01 ~]# dnf -4y --refresh update [root@katello01 ~]# dnf needs-restarting -r If there were any updates to foreman-related packages, make sure foreman is in a consistent state: [root@katello01 ~]# foreman-maintain service stop [root@katello01 ~]# foreman-installer --scenario katello When the katello services have started again, upgrade the release-rpms: [root@katello01 ~]# dnf -4y update https://yum.theforeman.org/releases/3.7/el8/x86...

I'm using ansible as a way of remote execution on my foreman / satellite servers. With version 3.5 (foreman) / 6.13 (satellite) I've found that the setting for 'ansible_ssh_private_key_file' is not permanently set after re-running 'foreman-installer'. First, verify that's actually your problem: [root@katello ~]# hammer --no-use-defaults settings info --name 'ansible_ssh_private_key_file' If the value returned is not correct, fix it by using the 'settings set'-subcommand: [root@katello ~]# hammer --no-use-defaults settings set --name 'ansible_ssh_private_key_file' --value '/var/lib/foreman-proxy/ssh/foreman-proxy-ecdsa' Ansible should now work, there's no restart of foreman-proxy required. Feel free to comment and / or suggest a topic.