Bug #35678
closedRun pulpcore-manager trim-rpm-changelogs during upgrades to pulp_rpm 3.17.5+
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2122344
In order to counter https://issues.redhat.com/browse/RHELDST-11565, in Satellite 6.10 we introduced a changelog limiting feature which restricted the number of changelogs saved into Satellite to the latest 10 (by default).
However this only applies to brand new installations. Any packages synced from the CDN prior to the application of that patch, or migrated from Pulp 2, will not be re-saved with this restriction in place. In effect this means that the package metadata saved for these old packages is larger than it needs to be by significant margins.
The impacts:
- more memory consumption during import / export operations [0]
- longer publishes [1]
- significant amounts of unnecessary disk space utilization [1]
We added a script which would clean up this unnecessary data, but nothing triggers it to be executed. It's something that only ever needs to be run once, so having "foreman-maintain upgrade" run it would result in waste.
Therefore we ought to document, as a one-time operation, running the following command (I believe this is correct):
sudo -u pulp PULP_SETTINGS='/etc/pulp/settings.py' /usr/bin/pulpcore-manager rpm-trim-changelogs
We can do this as a manual upgrade step for 6.12 but it can be run on any version 6.11+ (and on 6.10 with a slight tweak). Therefore we can also suggest this to any users who are encountering problems with these items as well.
[0] https://bugzilla.redhat.com/show_bug.cgi?id=2061224#c28
[1] https://github.com/pulp/pulp_rpm/pull/2333#issuecomment-1006024014