Actions
Bug #15377
closedchecksum-type does not updated on already synced repository at Satellite Capsule.
Status:
Closed
Priority:
High
Assignee:
Category:
Foreman Proxy Content
Target version:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1288656
Description of problem:
If the checksum-type for a custom repository is changed on the Satellite webUI, the repodata on the Satellite server works as expected, however the content synced to the Capsule does not get updated. The only way to get it updated, is to create a new content view and sync to the capsule. Note that creating a new version and promoting does not work. Must be a complete new content view.
Version-Release number of selected component (if applicable):
6.1.4
How reproducible:
100%
Steps to Reproduce:
1. Create a product and repository with sha256
2. Add this a lifecycle environment related to a capsule and sync it
3. Use pulp-admin or check the repodata created on the capsule and it will be using sha1256
4. Modify the repository to use sha1 and create a new version for the content view
5. Sync and check the repodata. On the Satellite server, repodata now will have sha1 however the capsule still has sha256
Actual results:
Capsule still has sha256
Expected results:
Capsule must reflect the configuration on the Satellite server
Additional info:
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/6116 added
Updated by Justin Sherrill over 8 years ago
- Priority changed from Urgent to High
- Translation missing: en.field_release set to 143
Updated by Justin Sherrill over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|57ab21e3d195e977e7844266ecd2572074cf6ef2.
Updated by Brad Buckingham over 8 years ago
- Category changed from 91 to Foreman Proxy Content
Actions