Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
This happens on a clean Centos 6.4 installation on VMWare Workstation 10 using minimal install from the net install ISO. After installing and removing the "Development tools" group, critical packages are removed and system crashes. System will not boot again.
Version-Release number of selected component (if applicable):
How reproducible:
It does this consistently. I have tried to do another clean install of Centos 6.4 with 'mininal' selected for packages and repeated the steps below to get the same result.
Steps to Reproduce:
1. Install fresh copy of Centos 6.4 x86_64 from the net install ISO from official Centos mirror.
2. yum groupinstall "Development Tools"
3. reboot
4. yum groupremove "Development Tools"
5. various critical packages are removed. In my case, including the removal of lvm2..
Actual results:
System freezes and will not boot after a cold restart.
Expected results:
Only development related packages removed using groupremove.
Additional info:
Some terminal output showing issue: http://pastebin.com/Pqa1teLD
Oh and btw removing binutils is quite ok, as that package is a part of the Development Tools group in CentOS. I have yet to figure out why is lvm getting removed but that will hopefully get more clear when I see your paste.
Forgot the paste had auto remove set. I don't have a copy of the original output but should be able to recreate that tomorrow. In the mean time, I invite you to install centos on a VM and give it a shot. The issue is consistent.
Ok, I'm pretty sure now this is not a bug in yum, it does exactly what it's required to do:
Development Tools group contains mandatory package binutils. By removing the group, you also remove this package. Now, module-init-tools require binutils so they have to be removed as well. And similarly, lvm2 requires module-init-tools, so it also has to be removed.
The way I see it, I install dev tools to compile something. I then uninstall dev tools. System breaks. Something isn't right. Do you not see how this could be an issue?
I do but it's simply not an issue of yum - it really does what it's asked to do. If you want a one-instance fix, setting groupremove_leaf_only=1 in yum.conf should help you.
If you want a permanent fix, I suggest contacting CentOS with a request to make this configuration default or to remove the binutils package from "Developer Tools" group.
HTH
Jan
The groupremove_leaf_only=1 workaround did not do the trick for me: http://pastebin.centos.org/6051/
However the guy's at #centos suggested yum history list/info/undo and that appears to achieve the desired goal. Hope this helps others.