Hide Forgot
Description of problem: It would be nice if when we had beta programs where people are running beta versions of RHEL, that auto-attaching subscriptions using subscription manager was smart enough to use their beta subscriptions before using up their production subscriptions. Could we leverage the new distribution.version.modifier to know when to do that? Would make it much simpler than forcing people to manually attach the beta subscription, or rolling the dice with auto-attach and removing any production subscription that gets pulled in.
I don't think that's a good idea. It sounds like we should have a separate beta product cert that is covered by beta product subscriptions. We only want to use these "beta subscriptions" on the rhel OS product, which seems weird. I'm not sure how to tell if a particular product (cert/id) is beta or not.
This was fixed by using a different product id for beta.