Thank you for linking to this PR!
And thank you @lakedh for your input aswell!
What i did, which also applies to new CV/CCV’s but would (should) be overwrote when you do an upgrade, is edit the python file that is parsed through:
edit
Make a copy of the original file, for easy safe keeping:
cp /usr/lib/python3.12/site-packages/pulp_rpm/app/serializers/repository.py ~/repository.py
Edit this file:
sudo vim /usr/lib/python3.12/site-packages/pulp_rpm/app/serializers/repository.py
Navigate to line 179, or find this specific piece of code the first occurance:
return data
like the PR does, we add to def to_representation(self, instance):
an if statement to make the "package_signing_fingerprint"
return an empty string, rather then NULL.
Just above the return, we add this:
# The current API field definition expects empty string for nullable values,
# but some migration paths can set an empty string to none in the database.
if data["package_signing_fingerprint"] is None:
data["package_signing_fingerprint"] = ""
You should have something like so:
Once that’s inplace, save and restart foreman so that any edits to the python file are also taken in: foreman-maintain service restart
Navigate to your (C)CV that is bugged. Do make sure to publish & promote the one where you still have packages in it!
Also, if you have troubles removing the invalide content-view, first try to
stop the current promotion, i had to force unlock and then cancel/resume it. If you have your OTAP environment on that bugged version withoud packages in it, promote and publish an older version to your OTAP line, that way you still have a working version published. You can do this by clicking the 3 dots next to the previous version with packages in it.
Once you have a properly clean (C)CV, try a manual publish and promote, it should work withoud any issues!