[Bug 813510] New: aaa_base/sysvinit: missing inittab makes system unrebootable
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c0 Summary: aaa_base/sysvinit: missing inittab makes system unrebootable Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: lnussel@suse.com ReportedBy: jengelh@inai.de QAContact: qa-bugs@suse.de CC: werner@suse.com, aj@suse.de Found By: Beta-Customer Blocker: --- systemd is installed by default starting from some openSUSE version N. The following bug applies to cases where an administrator (a) installed a version older than N, and continuously upgraded it over the years (e.g. 11.3->11.4->12.1->12.2->), implicitly keeping sysvinit the default init program, or (b) installed a version >= N and willfully post-installed and runs sysvinit. When upgrading from such an openSUSE system <= 12.2 with sysvinit active, (a) installation of aaa_base-12.3 will cause a removal of /etc/inittab (b) installation of sysvinit-2.88+ causes init to be reloaded Reloading init with a non-existent inittab is... without success: # zypper dup ... # reboot # (nothing happens) # cat /dev/vcs1 INIT: Switching to runlevel: 6 ... INIT: no more processes left in this runlevel and that makes sense, given /etc/inittab was just nuked. Not good. Suggestion: move inittab to the sysvinit package and release that as an update. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c1 --- Comment #1 from Jan Engelhardt <jengelh@inai.de> 2013-04-07 03:48:55 CEST --- Created an attachment (id=533870) --> (http://bugzilla.novell.com/attachment.cgi?id=533870) screenshot It seems that restoring /etc/inittab is not sufficient. More missing files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c2 --- Comment #2 from Ludwig Nussel <lnussel@suse.com> 2013-04-24 09:17:45 CEST --- maybe we should just remove the %post script that reloads init -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com AssignedTo|lnussel@suse.com |werner@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c3 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |lnussel@suse.com --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2013-04-24 07:38:15 UTC --- (In reply to comment #2) Why I have become assignee for this bug? It is a matter of fact that aaa_base for version >= N will not work together with sysvinit due changes I've not done within aaa_base, from changelog: Fri Oct 12 14:41:56 UTC 2012 - coolo@suse.com - update from git: * remove all files not necessary for systemd * move files to /usr and leave symlinks around - conflict with sysvinit To use sysvinit a) a /etc/inittab is required an b) a wrapper for systemd units has to be installed (indeed such a thing exists e.g. on Debian). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c4 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|lnussel@suse.com | --- Comment #4 from Ludwig Nussel <lnussel@suse.com> 2013-04-24 10:00:44 CEST --- According the the description init gets reloaded on update which causes the upgrade issue. OTHO the %post script of sysvinit looks like it checks whether init is still init so actually init should not have been reloaded. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c5 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |coolo@suse.com InfoProvider| |jengelh@inai.de --- Comment #5 from Dr. Werner Fink <werner@suse.com> 2013-04-24 08:18:42 UTC --- (In reply to comment #4) As already told: you can not install sysvinit with current aaa_base ... Stephan had removed all required file *without* porting it to sysvinit or a new sysvinit_base. The real question is: why Jan has installed sysvinit at all. Jan? To be exact: on my update from 11.4 to 12.3 I was not able to choose sysvinit without ignoring a conflict and without a further installation source. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c6 --- Comment #6 from Dr. Werner Fink <werner@suse.com> 2013-04-24 08:36:13 UTC --- Beside this on my 12.3 system here there exists a (temporary?) /etc/inittab which exactly one line which describes the current pseudo runlevel. Don's know which service or unit or rules creates this (maybe YaST2). It seems to required by the nfs dispatcher of the NetworkManager. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c7 Jan Engelhardt <jengelh@inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jengelh@inai.de | --- Comment #7 from Jan Engelhardt <jengelh@inai.de> 2013-04-29 23:48:21 CEST --- When upgrading to 12.3, systemd will be installed (if it is not already) and, as intended by openSUSE, will become the default on the next boot. This bug report solely concerns itself with the fact that a still-running sysvinit can no longer shutdown (and thus reboot in systemd) after zypper dup. Supplying the inittab file in the sysvinit package would seem a lot simpler than poking around in an otherwise working %post section (mind the sysvinit fanatics). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c8 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |coolo@suse.com --- Comment #8 from Dr. Werner Fink <werner@suse.com> 2013-04-30 06:52:38 UTC --- (In reply to comment #7) Hmm ... how can I patch an already installed sysvinit package not to remove but include an /etc/inittab? To make it clear, I've a backup of the latest files from aaa_base required by sysvinit[1] The only problem is that this does not help at an update. That this problem may happen I've already warned but no one had listen to me ;) Now I've become owner of a bug which I had not caused. @Coolo: How to solve your hard remove of e.g. /ertc/inttab and associated [1] For sysvinit fanatics: There are solutions around even to boot systemd units even with sysvinit. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c9 --- Comment #9 from Stephan Kulow <coolo@suse.com> 2013-04-30 11:27:55 CEST --- I hard removed these things to discover issues as this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c10 --- Comment #10 from Dr. Werner Fink <werner@suse.com> 2013-04-30 10:32:07 UTC --- (In reply to comment #9) ... hmmm ... and how can I fix this bug? Without an update before the update tits self it is not possible (IMHO). The running sysvinit can not reboot without /etc/inittab but this has been removed due to the update with zypper. The only way to update a sysvinit baseds system is to use a installation DVD as within a running system we run into a bootstrap problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c11 --- Comment #11 from Stephan Kulow <coolo@suse.com> 2013-04-30 13:22:48 CEST --- Can't aaa_base's %post create a dummy inittab if it notices sysvinit running? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c12 --- Comment #12 from Jan Engelhardt <jengelh@inai.de> 2013-04-30 13:23:00 CEST --- I think it should be fine just to put inittab back into %files. If you are one of the unfortunate ones to already have done the update and got a /etc/inittab.rpmsave, you already hit the bug and had to correct it by hand. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c13 --- Comment #13 from Stephan Kulow <coolo@suse.com> 2013-04-30 13:31:27 CEST --- btw, tons of systems were migrated from sysvinit to systemd by now with zypper dup. Jan is just the first to make a problem out of one unclean shutdown -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c14 --- Comment #14 from Dr. Werner Fink <werner@suse.com> 2013-04-30 12:14:04 UTC --- (In reply to comment #13) Nevertheless Jan report is fully correct and if we want to go forward to SLES12 this problem should be fixed. That is even if most openSUSE users are familiar with such problems but only one user reports this it remains a bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c15 --- Comment #15 from Jan Engelhardt <jengelh@inai.de> 2013-04-30 14:20:24 CEST --- created request id 173964 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c16 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|coolo@suse.com |jengelh@inai.de --- Comment #16 from Dr. Werner Fink <werner@suse.com> 2013-04-30 13:37:46 UTC --- (In reply to comment #15) ??? AFAIK sysvinit will be removed on update to 12.3 ... how do you think does the /etc/inittab will become part of the file system on the disk? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c17 Jan Engelhardt <jengelh@inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jengelh@inai.de | --- Comment #17 from Jan Engelhardt <jengelh@inai.de> 2013-04-30 15:49:13 CEST --- I do not see that happening in a 12.1 test VM pointing to 12.3 and ready for `zypper dup --no-r`. aaa_base only conflicts with sysvinit-init (provider of the /sbin/init symlink), but not sysvinit itself. From that I infer: 1. the continued presence of sysvinit would not cause a dependency issue (packages may get selected for removal if dependencies of theirs have gone away) 2. I think there may be a "delete-me list" in the distro, which is used to get rid of packages which would otherwise stay around forever (see #1), such as libmpc2. If this thesis is correct, sysvinit is not part of this list either. Therefore, shipping /etc/inittab in sysvinit looks about right, because the package continues to be present in the system (at least for now). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c18 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jengelh@inai.de --- Comment #18 from Dr. Werner Fink <werner@suse.com> 2013-04-30 14:52:18 UTC --- And do you have test this out? That a) is the file /etc/inittab still there after `zypper dup --no-r' .. *and* b) are you able to reboot even if the boot scripts /etc/init.d/rc, /etc/init.d/halt, /etc/init.d/reboot are gone? My plan was to provide a further sysvinit-filesystem which would then include all required file and which it self is required by sysvinit. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c19 Jan Engelhardt <jengelh@inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jengelh@inai.de | --- Comment #19 from Jan Engelhardt <jengelh@inai.de> 2013-04-30 17:05:55 CEST --- b) no, but I mentioned that in comment #1 already. It would, I think, just be a matter of putting the init.d files in sysvinit as well. Nothing against a sysvinit-filesystem package, but nothing for it either (I do not think openSUSE supports alternate sysv implementations like openrc). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c20 --- Comment #20 from Dr. Werner Fink <werner@suse.com> 2013-04-30 15:29:45 UTC --- (In reply to comment #19) With b) your are going down with a busy file system ... sorry but (IMHO) we should not support this. The only clean way to update a sysvinit based system is to use a installation DVD. You may add a test of existence of /etc/inittab in the %post scriptlet ... but this also will not allow you to run a clean shutdown. For this a special /etc/inittab is required to run a clean shutdown. And for this I would suggest to readd /sbin/quick_reboot, /sbin/quick_halt, and /sbin/quick_poweroff to the file list which could be used in this dummy /etc/inittab. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c21 --- Comment #21 from Jan Engelhardt <jengelh@inai.de> 2013-05-03 08:19:54 CEST ---
With b) your are going down with a busy file system
It would not be any busier before systemd made it into openSUSE, would it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=813510 https://bugzilla.novell.com/show_bug.cgi?id=813510#c22 --- Comment #22 from Dr. Werner Fink <werner@suse.com> 2013-05-03 06:46:05 UTC --- (In reply to comment #21) Without /etc/init.d/boot.localfs and /etc/init.d/halt the file systems will be not umounted nor unmounted in correct order nore there will be a sync before reset. With /sbin/quick_reboot there is a better chance not to see a broken file system as it try to unmount network based file systems like NFS and the local file systems. Even md raids and lvm will be handled by be /sbin/quick_reboot ... belive me this is better than simply than a hard `reboot -d -f' -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com