Description of problem:
If a CV exists, with both RHEL6 and RHEL7 base repos in it, a system connected to the CV will only 'see' the repos that match the version of RHEL installed on the system.

For custom products, this does not work.

This is especially cumbersome in container environments. 

My customer, for example, has Atomic Host nodes connected to the Default Library View (to get access to new RPMs as soon as we release new container images).

In that Default Org View are also EPEL6 and EPEL7. RHEL6 containers nicely only 'see' and enable the RHEL6 base repos, but they have both EPEL6 and EPEL7 enabled. Same goes for RHEL7 containers, but the other way around.

This is cumbersome.

As I discussed with Rich Jerrido, it would be useful if we could inject some specific tags into the custom product and product certificate that makes sure that on RHEL6 containers (or VMs) only EPEL6 is enabled, and on RHEL7 containers (or VMs) only EPEL7 is enabled, even though both are available from the same CV.

Hope this makes sense :)


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


How reproducible:


Steps to Reproduce:
1. Add both RHEL6 and RHEL7 base repos, EPEL6 and EPEL7. Sync all.
2. Connect new system to Default Org View
3. Spin up RHEL6 or RHEL7 container

Actual results:
Container sees only appropriate RHEL6 *or* RHEL7 content, but both EPEL6 *and* EPEL7.

Expected results:
Container sees only appropriate RHEL6 *or* RHEL7 content, and only appropriate EPEL6 *or* EPEL7.

Additional info: