Red Hat Bugzilla – Bug 248913
yum update while running a kernel.org kernel causes f7-3228 to fail to boot
Last modified: 2014-01-21 17:59:00 EST
Description of problem: after booting to a non fedora kernel, I got an updates-available notification, and I updated. Then I rebooted to fedora kernel, and it dropped me into 'repair-filesystem' shell. I ran fsck on / and /boot, no errors. After fiddling for a while, I rebooted with enforcing=0 on boot-line, and it relabeled all the files, then continued and booted successfully. It then rebooted fine to f7-3228 kernel w/o further intervention. Version-Release number of selected component (if applicable): yum-3.2.1-1.fc7 kernel-2.6.21-1.3228.fc7 How reproducible: tedious (at least) to try to reproduce, since it would require another round of updating while running a non-Fedora kernel. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Ive filed this as a yum problem since it started the problem, though perhaps the fix really should be elsewhere Possible fixes, mitigations - 1- Warn that update under non selinux kernel would break the current security context 2- improve the 'repair-filesystem' notification to explain the selinux connection, eliminating the fumbling 3- re-run the selinux relabel after yum-update, under non-selinux kernel (if that works) thanks
post hoc ergo propter hoc doesn't apply here. this should probably live over in mkinitrd space.
Ive repeated this test using latest updates (inc new 22.1-27 kernel), and with previous 3228 also. IE I booted to the kernel.org kernel, then pupdated 19 packages, and rebooted to both f7 kernels, which both dropped to repair-filesystem shell. Then rebooted to -27 after adding 'enforcing=0', and -27 then did the relabelling, and got me booting normally again.
This has nothing to do with mkinitrd at all... I'm guessing initscripts is the right place to handle this need for a re-label.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.