Description of problem:

After upgrading Satellite from 6.10 to 6.11 and then 6.12, when running a refresh of the manifest, the Subscription Allocation type, which indicates the Satellite version to be used, is changed automatically to 6.15, which causes a failure in Satellite to identify and enable any repository. This seems pretty much a bug regression of the following, with the difference of getting the version higher, not lower:

https://access.redhat.com/solutions/5039851

https://bugzilla.redhat.com/show_bug.cgi?id=1823905

How reproducible:

Upgrading from 6.10, to 6.11 and then 6.12. Bug not found in a fresh install.

Is this issue a regression from an earlier version:

Probably yes, from 6.7

Steps to Reproduce:

1. Upgrade Satellite from 6.10, to 6.11 and finally 6.12, changing the Subscription Allocation type accordingly along the way.
2. When in 6.12, click the Refresh button to refresh the Manifest.
3. Check the Subscription Allocation type and the version will be set as 6.15.
4. Satellite will throw a SSL error accusing the version to be wrong and no repository is able to be accessed or enabled.

Actual behavior:
Refreshing a Manifest is automatically changing the Subscription Allocation type.

Expected behavior:
The Subscription Allocation type should only be changed manually, not after a Manifest refresh in Satellite.

Business Impact / Additional info:

The business impact is that Satellite won't allow enabling any repository, thus impacting any delivery that needs a new repository.