[Bug 1174272] Re: 'reboot now' reverting to maintenance mode, instead of rebooting
Launchpad Bug Tracker
1174272 at bugs.launchpad.net
Fri Jun 20 12:40:44 UTC 2014
This bug was fixed in the package upstart - 1.12.1-0ubuntu10
---------------
upstart (1.12.1-0ubuntu10) utopic; urgency=medium
* Revert spurious +x -> -x change on daily upstart cron file.
* Cherrypick reboot command fix to not process REBOOTCOMMAND argument
when in runlevels 2-5 and without using force flag. (LP: #1174272)
-- Dimitri John Ledkov <xnox at ubuntu.com> Fri, 20 Jun 2014 12:09:51 +0100
** Changed in: upstart (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now' reverting to maintenance mode, instead of rebooting
Status in Upstart:
In Progress
Status in “upstart” package in Ubuntu:
Fix Released
Status in “upstart” source package in Trusty:
In Progress
Bug description:
[Impact]
* reboot(8) command has behaviour different from the documented one,
in particular when passing optional REBOOTCOMMAND argument, whilst not
in runlevel 0 or 6 and without passing --force, shutdown(8) was not
invoked with the appropriate arguments. Actual behaviour was dropping
to runlevel 1, instead of the expected reboot.
[Test Case]
* Whilst booted normally to runlevel 2, after executing:
$ sudo reboot please
* machine should complete reboot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1174272/+subscriptions
More information about the foundations-bugs
mailing list