createrepo_c, createrepo_c-libs and tfm-pulpcore-python3-createrepo_c package have been updated to version 0.21-1 (from 20.0-2)
tfm-pulpcore-python3-pulp-rpm to version 3.18.3-1 (from 3.17.10-3)
Since then (after restarting services) syncing repo end with status Sync Incomplete and error:
Katello::Errors::Pulp3Error: column rpm_modulemd.profiles does not exist
LINE 1: …lemd".“dependencies”, “rpm_modulemd”.“artifacts”, "rpm_modul…
Sync works with updated versions
Foreman and Proxy versions:
Foreman and Proxy plugin versions:
Distribution and version:
CentOS Linux release 7.9.2009
Other relevant data:
Downgrading packages and restarting services is a working workaround.
How did you upgrade? Was the installer run after the packages have been updated?
Updates was updated via yum from official pulpcore repo.
I didn’t run foreman installer after the installation (yum-cron runs on the server)
(Last time it didn’t help Pulpcore services failed)
If you didn’t run the installer, the DB migrations were not applied and thus things fail.
Please re-try with an installer run.
It’s worst !
Hammer ping returns me:
Server Response: Message: Pulp redis connection issue at https://myserver/pulp/api/v3.
Check whether all services are running using the ping call: [FAIL]
Some components are failing: pulp3
The 5 tries to restart the service failed
Ah yes, you’re on 4.5, which didn’t yet get the fix for that.
foreman-installer --foreman-proxy-content-pulpcore-cache-enabled true
If I remember correctly
foreman-installer --reset-foreman-proxy-content-pulpcore-cache-enabled should fix this. There was a change regarding the default.
The fix is not (yet) backported to Foreman 3.3 / Katello 4.5. One need to use
--foreman-proxy-content-pulpcore-cache-enabled true until then
Thanks! I completely forget to check that point! Yet it’s write on my upgrade doc since I have already been facing this trouble
Perfect. So you’re back at a working, fully uptodate system?
And yeah, please don’t update packages w/o running the installer, this is asking for trouble
Yes, it’s now working with the system up to date.
I will shut yum-cron to avoid this situation.