Description of problem: after updating to initscripts-8.31.1-1 /ect/inittab gots deleted and I /etc/inittab.rpmsave got created instead. (no bootable system!) Version-Release number of selected component (if applicable): 8.31.1-1 How reproducible: always Steps to Reproduce: 1. boot 2. 3. Actual results: no inittab file found Expected results: inittabfile should be found an not dropped by an update (this may even break fc3/4->fc5 updates) Additional info: please mark this as a blocker
What were you upgrading from?
I had this problem too, upgrading from initscripts.i386 8.31-1
We're trying to duplicate this here w/ anaconda upgrades from FC4 to the current release candidate of FC5.
this info might help: my rawhide install was installed in textmode so it defaulted to runlevel 3 and I edited it to be 5 (could it be deleting edited files only?)
Is SELinux enabled, and are there any AVC messages? How did you upgrade - anaconda, yum , or straight RPM? Was there any messages about saving files as .rpmsave or installing them as .rpmnew? I can't reproduce this here on a simple 8.31-1 -> 8.31.1-1 upgrade.
(In reply to comment #5) > Is SELinux enabled, and are there any AVC messages? > enabled no avcs > How did you upgrade - anaconda, yum , or straight RPM? > pup > Was there any messages about saving files as .rpmsave or installing them as .rpmnew? > pup does not show such infos :( > I can't reproduce this here on a simple 8.31-1 -> 8.31.1-1 upgrade.
I can't reproduce either, selinux enabled, using pup, edited /etc/inittab. Any text spew from pup will end up in your X session log (/tmp/xses.* usually)
(In reply to comment #7) > I can't reproduce either, selinux enabled, using pup, edited /etc/inittab. > > Any text spew from pup will end up in your X session log (/tmp/xses.* usually) too late :( currently installing fc4 on that box to test anaconda update...
Can you reproduce it at will by downgrading, moving in your rpmsave file, and upgrading?
Also, did you have *any* third party packages installed?
Created attachment 126163 [details] yum.log illustrating bad upgrade Per discussion on the test list, it looks like yum went and uninstalled my initscripts, which would explain the behaviour... I'll attach the complete yum.log now. I have only two "third-party" packages installed: the Cisco VPN client, and VMWare, but I just reinstalled them and they don't touch /etc/inittab.
Thanks, do you have any yum plugins installed/enabled. Can you also attach /var/log/rpmpkgs*
Julian, also if you rollback initscripts to previous version and update does it recurr?
(In reply to comment #12) > Thanks, do you have any yum plugins installed/enabled. Can you also attach > /var/log/rpmpkgs* The only plugin installed/enabled is "installonlyn" which is what came with FC4... I'm not too clear on what this does and what its impact might be. I'll attach the /var/log/rpmpkgs* output now
Created attachment 126167 [details] rpmpkgs file
(In reply to comment #13) > Julian, also if you rollback initscripts to previous version and update does it > recurr? Paul - can you advise where I could get the old build of initscripts I will try this and let you know.
(In reply to comment #10) > Also, did you have *any* third party packages installed? first: does not happend using anaconda... 2: I had no third party packages installed ; clean rawhide box with some packages from extras.
Created attachment 126244 [details] old initscripts rpm Here's the old version of initscripts.
I tried to reproduce the behaviour by installing the old initscripts and doing a yum update, but the problem did not reoccur.
*** Bug 185731 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 197906 ***