Bug 2055808

Description of problem:

Upgrading the Satellite 7.0 from Snap 8 to Snap 9 , sets the CDN configuration for all Organizations in airgapped mode

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

Satellite 7.0 [ snap 8 and snap 9+ ]


How reproducible:

Always with snap 8 to snap 9 upgrade

Steps to Reproduce:
1. Install snap 8 of Satellite 7.0 someway.
2. Import mainfest and Enable certain repos + sync
3. Take a look at "Content --> Subscriptions --> Manage Manifest --> CDN Configuration" page. 
4. Now, upgrade  the snap 8 instance to snap 9 using satellite-maintain or any other way.
5. Go to "Content --> Subscriptions --> Manage Manifest --> CDN Configuration" page.
6. Go to "Content --> Red Hat Repositories" page

Actual results:

Step 3, You will get to see just one option there having URL\Username\Password\Org Label\SSL CA COntent Creds [ Check attached screenshot old.png  ]

Step 5. You will get to see Three options but Air-Gapped is selected by default.  [ Check attached screenshot new.png  ]

Step 6: "CDN configuration is set to Air-gapped (disconnected). Repository enablement/disablement is not permitted on this page." 


Expected results:

Unless the disconnected_mode was enabled for the lower version of the satellite, Upgrading the Satellite to z stream of 7.0 should always point to "Red Hat CDN" configuration for the manifest. 


Additional info:

When this happens and we are not aware of the fact why, 

* We will not be able to enable any repos.

* A disconnected satellite who was perhaps consuming the content from a connected satellite using ISS, will no longer be able to enable any repos via ISS or sync the existing repos. 


The sole purpose of opening this BZ is that I suspect, those who are upgrading from Satellite 6.10 to 7.0, they could run into the same issue. I could not test this scenario due to https://bugzilla.redhat.com/show_bug.cgi?id=2053970 but I plan to test once the upgrade bug gets fixed.