My latest understanding is that once merged (and once the build pipeline is then run) the RPM will be available in Index of /pulpcore/3.22 which is in use for the released version 4.8, and will also be used for the soon to be released 4.9.
However, it cannot be used for Katello 4.7 and older, since those use a older pulpcore version than 3.22.
Note that the corresponding API bindings are not yet in the Katello 4.8 repo (this has been merged so it should be along with the next run of the Katello 4.8 build pipeline). In case this causes problems, you can already obtain the client gem from the nightly Katello repo (if you go this route make sure you only grab this one RPM from the nightly repo):
Once you have installed the two RPMs on your Katello 4.8 installation, you must re-run foreman-installer to ensure the Pulp DB migrations are applied. You can check on the status of the pulp_deb migrations in particular by running PULP_SETTINGS=/etc/pulp/settings.py pulpcore-manager showmigrations deb.
Once your services are back up orphan cleanup will be working once more.
# foreman-maintain packages check-update
Running Check for available package updates
================================================================================
Check for available package updates:
Updating Subscription Management repositories.
This system is registered with an entitlement server, but is not receiving updates. You can use subscription-manager to assign subscriptions.
Last metadata expiration check: 0:26:10 ago on Thu 11 May 2023 11:16:22 AM CEST.
python39-pulp-container.noarch 2.14.5-1.el8 pulpcore
python39-pulp-deb.noarch 2.20.2-1.el8 pulpcore
rubygem-foreman_ansible.noarch 11.2.0-1.fm3_6.el8 foreman-plugins
[OK]
--------------------------------------------------------------------------------
Note that it turns out that until Katello 4.8.1 is released, the repos used by Katello 4.8, are missing the new rubygem-pulp_deb_client-2.20.2-1.el8.noarch.rpm to go with the patched pulp_deb version python39-pulp-deb-2.20.2-1.el8.noarch.rpm (which is available for Katello 4.8).
Apparently this causes problems during regular pulp_deb usage. See this post for a workaround.
Hi, after upgrading to Katello 4.8.1 (OS: RHEL 8.6, Foreman: 3.6.1) i am getting this error by Remove Orphans:
There was an issue with the backend service pulp3: Connection reset by peer - SSL_connectThere was an issue with the backend service pulp3: Connection reset by peer - SSL_connect
I am not sure from the pastebin you posted, (see if you can find a pulp task backtrace/error in your failed Foreman task), but my gut feeling is that this is a different issue than the one described in this thread.
I have double checked that Katello 4.8.1 has access to every part of the pulp_deb fix. If you have successfully upgraded to this version, it is not really possible to still be getting the original orphan cleanup error from this thread (of course it is entirely possible to be hitting some different issue).
Things you can check to verify if you are relevantly upgraded:
Is python39-pulp-deb-2.20.2-1.el8.noarch.rpm installed on your system?
Is rubygem-pulp_deb_client-2.20.2-1.el8.noarch.rpm installed on your system?
Try running PULP_SETTINGS=/etc/pulp/settings.py pulpcore-manager showmigrations deb and check that all pulp_deb migrations are applied.
Check if all services are running properly: foreman-maintain service status
(“Cannot delete some instances of model ‘Content’ because they are referenced through protected foreign keys: ‘Package.content_ptr’.”, {<RepositoryContent: pk=f0f6e1cf-c3f1-41ee-ad7e-ca2f0e0f1266>})