Createrepo_c updates break repo sync

Support
,
1

Problem:
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…

Expected outcome:
Sync works with updated versions

Foreman and Proxy versions:
Foreman 3.3.0
Foreman and Proxy plugin versions:
|plugins|version|
|—|—|—|—|
|foreman-tasks |6.0.2|
|foreman_puppet |4.0.1|
|foreman_remote_execution |7.1.1|
|katello |4.5.0|

Distribution and version:
CentOS Linux release 7.9.2009
Other relevant data:
Downgrading packages and restarting services is a working workaround.

2

How did you upgrade? Was the installer run after the packages have been updated?

3

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)

4

If you didn’t run the installer, the DB migrations were not applied and thus things fail.

Please re-try with an installer run.

5

It’s worst !
Hammer ping returns me:

pulp3:
Status: FAIL
Server Response: Message: Pulp redis connection issue at https://myserver/pulp/api/v3.

Foreman-maintain:
Check whether all services are running using the ping call: [FAIL]
Some components are failing: pulp3

The 5 tries to restart the service failed

6

Ah yes, you’re on 4.5, which didn’t yet get the fix for that.

Workaround: foreman-installer --foreman-proxy-content-pulpcore-cache-enabled true

2 Likes
7

If I remember correctly foreman-installer --reset-foreman-proxy-content-pulpcore-cache-enabled should fix this. There was a change regarding the default.

8

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

9

Thanks! I completely forget to check that point! Yet it’s write on my upgrade doc since I have already been facing this trouble

10

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 :frowning:

11

Yes, it’s now working with the system up to date.
I will shut yum-cron to avoid this situation.

1 Like