Description of problem:
It makes sense that we block users from installing groups they haven't subscribed to, but it doesn't make sense that they can't become compliant by removing the groups they don't have subscriptions for.
This is most obvious when you select a repo in anaconda, such as "Load Balancer" and then after the install, RHSM complains that you aren't compliant. At that point you cannot just remove "Load Balancer" with yum, you have to subscribe first.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Subscribe to Load Balancer
2. yum groupinstall "Load Balancer"
3. unsubscribe from "Load Balancer"
4. yum groupremove "Load Balancer"
"No group named Load Balancer exists"
group Load Balancer is removed.
This is not something we can fix in RHSM. We would need to enhance Anaconda and yum to drop down all the metadata. Can we close this and we can open up some RFE's against yum and anaconda if you feel strongly about this.
I am not quite convinced that this can't be fixed in RHSM. For instance, you could change the design so that repo metadata is cached (currently it isn't). Or have some repo that only gives group definitions, that is always installed. Something like that.
At any rate, I'd understand if the disruption of trying to fix this is more trouble than the fix is worth. But in that case, let's close this as WONTFIX.
OK.. will do that.
Note that I recently did a beta release of "groups as objects":
...which can be ready and turned on for 6.1.
It's a significant change, but it's "only" 6.1, and it should solve this problem (and is, I think, more what people want than what we currently do).