Plugins » Katello

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2106000

Description of problem:

We have seen a few bugs where the environment-content association in Candlepin gets somehow lost or corrupted, for example https://bugzilla.redhat.com/show_bug.cgi?id=2064979 and https://bugzilla.redhat.com/show_bug.cgi?id=1931027

Katello tracks the info it needs to recreate this data on Candlepin back-end but it is not accessible to the user without re-promoting Content Views, which is painful and contains many steps not actually necessary to fix the issue

Building the same logic into Manifest Refresh makes sense as this is often when the issue occurs / can potentially repair before it ever becomes a problem

Version-Release number of selected component (if applicable):

How reproducible: 100% (using https://bugzilla.redhat.com/show_bug.cgi?id=2064979 )

Steps to Reproduce: ( https://bugzilla.redhat.com/show_bug.cgi?id=2064979 )
1. Create a lifecycle path and content view, publish and promote some CV versions
2. Register the client in some LCE and CV
3. Enable repos on the client, try to install some package
4. Remove all subscriptions from the manifest and refresh it
5. Refresh the manifest a 2nd time (to produce the conditions of https://bugzilla.redhat.com/show_bug.cgi?id=2064979 )
6. Add subscriptions back to the manifest
7. Refresh the manifest again, one or more times
8. Sub-man refresh and re-subscribe the client, try to enable repos and install the same package as before
9. Register some new client in same CV and LCE, try to enable repos and install the same package as before

Actual results:

1. Client remained registered in the same CV and LCE but could not enable repositories or download package, due to entitlement certificate not providing content in this CV/LVE
2. Newly registered client has same issue

Expected results:

1. Manifest Refresh task should Warn the user if content access was removed in some CV/LVE
2. Once new entitlements are added and manifest is refreshed again, entitlement cert should provide the same repository access in this CV/LCE as it did as before the backend Candlepin issue occurred -- without requiring CV version repromotion

Additional info: