[Bug 985755] Re: /lib/init/upstart-job does not handle lucid->precise upgrade scenario

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.5-0ubuntu7

---------------
upstart (1.5-0ubuntu7) precise-proposed; urgency=low

  * Correct a build failure from the previous upload.

upstart (1.5-0ubuntu6) precise-proposed; urgency=low

  * debian/upstart.logrotate: don't create empty files after rotation;
    upstart will automatically create new log files for jobs as needed.
  * init/main.c: restore the fix for bug #540256; we know the console setup
    is taken care of by plymouth in Ubuntu, so upstart changing the console
    settings just makes trouble (such as turning echo back on when it
    shouldn't be).  LP: #876626.

  [ James Hunt ]
  * debian/upstart-job: Only attempt to handle disabled jobs if the running
    version of Upstart supports such a query (LP: #985755, #984474).
  * debian/manpages/upstart-events.7: Fixed typo and corrected reference to
    'kill signal' stanza.
 -- Steve Langasek <steve.langasek at ubuntu.com>   Thu, 26 Apr 2012 07:48:17 -0700

** Changed in: upstart (Ubuntu Quantal)
       Status: Confirmed => 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/985755

Title:
  /lib/init/upstart-job does not handle lucid->precise upgrade scenario

Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Precise:
  Fix Committed
Status in “upstart” source package in Quantal:
  Fix Released

Bug description:
  [Impact]
  If an upgrade from lucid to precise pulls in a new upstart job that should be started on package install, the job will silently fail to be started.  If other packages expect the job to be running, this may cause cascading installation failures.

  [Development Fix]
  Package will be copied to quantal when the archive opens.

  [Test Case]
  1. Install Ubuntu 10.04 desktop
  2. upgrade to 12.04 without rebooting.
  3. run /etc/init.d/cron stop; /etc/init.d/cron start
  4. verify that an error message is output and cron is not restarted.
  5. install the upstart package from precise-proposed.
  6. again run /etc/init.d/cron start
  7. verify that no error is output and cron is restarted successfully.

  [Regression Potential]
  None foreseen.

  
  /lib/init/upstart-job was recently changed (bug 974147) such that it now calls 'initctl show-config -e $JOB'. This works fine for precise systems and for oneiric->precise upgrades, but does not work for lucid->precise upgrades since 'show-config' is not a legitimate initctl command on the version of init running on lucid at the time of the precise upgrade (0.6.5-8) since the 'show-config' command was added in Upstart 1.3.

  /lib/init/upstart-job needs to be changed to handle the lucid upgrade
  path scenario by either checking the running version of init or more
  intelligently parsing the output of 'initctl show-config -e $JOB'
  since currently, an upgrade from lucid to precise will cause all
  upgraded packages containing upstart jobs to *not* restart the
  services.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/985755/+subscriptions