-
Bug
-
Resolution: Done-Errata
-
Major
-
6.16.0
Description of problem:
After upgrading from Satellite 6.15 to Satellite Stream, any repositories that were set to use SHA1 for the metadata checksum will remain being sha1 when the checksum type is changed to "Default". This is reproducible even after changing the metadata type to something else like sha512.
How reproducible:
100% (at least on a reproducer from QE)
Is this issue a regression from an earlier version:
Yes, 6.15.
Steps to Reproduce:
1. On 6.15 create some repositories with SHA1 metadata checksums
2. Upgrade to Stream
3. Choose one repo and change the checksum type to default without touching anything else before hand.
4. Check the publication
5. See that the publication is still sha1
6. Change the metadata checksum to sha256 and back to Default
7. See that it's still sha1
8. Try to make a new publication for the same repository version via the API and see that, even though no sha1 reference is passed in and the repository in Pulp doesn't refer to sha1, the publication is for some reason sha1.
Actual behavior:
Publication is still sha1
Expected behavior:
Publication should be anything besides sha1
Business Impact / Additional info:
Message iballou@redhat.com or vsedmik@redhat.com for a reproducer. This currently is reproducible on Pulp-RPM 3.25. We have since upgraded to Pulp-RPM 3.26, but nothing in the changelog makes me think the new version would be different.
- links to
-
RHBA-2024:140284 Important: Satellite 6.16.0 release