1. Proposed title of this feature request
Provide ability to subscribe hosts to older versions of a CV

2. Who is the customer behind the request?

3. What is the nature and description of the request?
Customer is requesting the ability for Satellite hosts to choose the version of the content view that they consume.

4. Why does the customer need this? (List the business requirements here)
The UNIX engineering team of the customer produces a new release of the OS on a regular basis.
Other engineering teams within the customer produce releases of their software stacks that are combined with the OS release.
The release cadences of the OS release and the cadence of the different software stacks are unaligned.

Each application team must perform testing before the OS release + app stack release is allowed to production.
Delays can happen during the testing phase, as a result different production systems require different versions of the OS release depending on their progress on testing.

For example, OS build 41 is combined with app A build 7 and app B build 9 and testing for the two stacks beings.
Testing for app A is successful and OS 41 + A 7 can be made available to production systems.
Testing for app B encounters issues and OS 41 + B 9 can not reach production.
As a result, we have some production systems that need OS 41 while others need to remain at OS 40.

Eventually UNIX eng produce OS 42, and issues in OS 41 + B 9 are resolved.
Testing of OS 42 + A 7 is again successful and OS 42 + A 7 can be pushed to production systems, but application stack B needs to stay at previous OS 41 since that's the latest OS release where the testing was successful.

5. How would the customer like to achieve this? (List the functional requirements here)
subscription-manager is able to list the versions of the CV that the host is subscribed to alongside their description.
subscription-manager is able to change the version of the CV that the host can consume.

Alternatively the version of the CV that hosts can consume can be modified via API / hammer.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
subscription-manager can list the versions of the assigned CV alognside their description.
subscription-manager can change the version of the assigned CV that the host consumes. Alternatively, the same can be accomplished via API / hammer.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
None found.

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Satellite 7

9. Is the sales team involved in this request and do they have any additional input?
No.

10. List any affected packages or components.
Multiple.

11. Would the customer be able to assist in testing this functionality if implemented?
Yes, certainly.