Foreman 3.9 update - Puppet Service resources failed

Support
1

Problem:
After updating from version 3.8 to 3.9 and running
#foreman-installer --scenario katello
I getting the message that 2 errors occurred, any thoughts ?

Error 1: Puppet Service resource ‘pulpcore-api.service’ failed. Logs:
/Service[pulpcore-api.service]
Starting to evaluate the resource (1932 of 2014)
Skipping restart; service is not running
Triggered ‘refresh’ from 2 events
The container Systemd::Unit_file[pulpcore-api.service] will propagate my refresh event
Evaluated in 0.57 seconds
/Stage[main]/Pulpcore::Service/Pulpcore::Socket_service[pulpcore-api]/Systemd::Unit_file[pulpcore-api.service]/Service[pulpcore-api.service]/ensure
change from ‘stopped’ to ‘running’ failed: Systemd start for pulpcore-api.service failed!
journalctl log for pulpcore-api.service:
– Logs begin at Mon 2024-01-22 11:24:21 EET, end at Mon 2024-01-22 11:35:48 EET. –
Jan 22 11:35:48 mar-linux-repo01 systemd[1]: Starting Pulp API Server…
Jan 22 11:35:48 mar-linux-repo01 systemd[1]: pulpcore-api.service: Main process exited, code=exited, status=203/EXEC
Jan 22 11:35:48 mar-linux-repo01 systemd[1]: pulpcore-api.service: Failed with result ‘exit-code’.
Jan 22 11:35:48 mar-linux-repo01 systemd[1]: Failed to start Pulp API Server.
Error 2: Puppet Service resource ‘pulpcore-content.service’ failed. Logs:
/Service[pulpcore-content.service]
Starting to evaluate the resource (1941 of 2014)
Skipping restart; service is not running
Triggered ‘refresh’ from 3 events
The container Systemd::Unit_file[pulpcore-content.service] will propagate my refresh event
Evaluated in 0.48 seconds
/Stage[main]/Pulpcore::Service/Pulpcore::Socket_service[pulpcore-content]/Systemd::Unit_file[pulpcore-content.service]/Service[pulpcore-content.service]/ensure
change from ‘stopped’ to ‘running’ failed: Systemd start for pulpcore-content.service failed!

Other relevant data:

2

Did you solve this? I ran into a similar state today, upgrading 3.8 → 3.9 on RHEL 8.

3

nop :frowning:
I have this issue now, although managed to update proxy is in 3.8 while foreman in 3.9.3

image
image706×131 7.44 KB

Run the following commands

dnf clean all
dnf install https://yum.theforeman.org/releases/3.9/el8/x86_64/foreman-release.rpm
dnf install https://yum.theforeman.org/katello/4.11/katello/el8/x86_64/katello-repos-latest.rpm
dnf install https://yum.puppet.com/puppet7-release-el-8.noarch.rpm
dnf install foreman-installer-katello
foreman-installer --scenario katello

4

Used the docs from here and at last it worked…

https://docs.theforeman.org/3.9/Upgrading_Project/index-katello.html#upgrading_a_connected_foreman_server_upgrading-connected

5

We solved our issue, too: The problem we had was how we executed the dnf update step while upgrading.

By mistake we only updated present packages without installing new ones (by using ansible.builtin.yum with “update_only” directive), which prevented all the pulpcore package obsoletions to be performed properly.

Additionally we had to install a dependency beforehand: ‘python3.11-setuptools’

Just in the unlikely case it helps someone.

2 Likes