RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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):


How reproducible:
always

Steps to Reproduce:
1. Subscribe to Load Balancer
2. yum groupinstall "Load Balancer"
3. unsubscribe from "Load Balancer"
4. yum groupremove "Load Balancer"
  
Actual results:
"No group named Load Balancer exists"

Expected results:
group Load Balancer is removed.

Additional info:

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":

http://lists.baseurl.org/pipermail/yum-devel/2010-December/007740.html

...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).