[Bug 1303891] Re: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.12.1-0ubuntu4

---------------
upstart (1.12.1-0ubuntu4) trusty; urgency=medium

  [ Adam Conrad ]
  * Disable chroot sessions by default, add an option to enable chroot
    sessions. (LP: #1277594)
 -- Dimitri John Ledkov <xnox at ubuntu.com>   Fri, 11 Apr 2014 22:31:21 +0100

** Changed in: upstart (Ubuntu Trusty)
       Status: Fix Committed => 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/1303891

Title:
  new initctl should fallback to old reload signal semantics, if pid1
  doesn't export reload dbus method

Status in Upstart:
  Fix Committed
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * Between upgrading upstart to trusty and rebooting: reload (initctl
  reload) commands fail and do not SIGHUP upstart jobs.

  [Test Case]

   * with pid1 being precise init, attempt to perform $ initctl reload
  against any job using trusty's initctl

  [Regression Potential]

   * Minimal, this re-introduces a previously removed code-path as
  fallback when reload signal delivery fails.

  [Other Info]

   * original bug report below

  new initctl should fallback to old reload signal semantics, if pid1
  doesn't export reload dbus method

  as per comment
  https://bugs.launchpad.net/upstart/+bug/893021/comments/2

  I'm currently testing Precise to Trusty upgrades and encountered - while troubleshooting bug http://pad.lv/1301962 - this issue:
  # initctl reload dbus
  initctl: Method "Reload" with signature "" on interface "com.ubuntu.Upstart0_6.Instance" doesn't exist

  The issue at hand is that during the upgrade the 'upstart' package
  will be updated but Precise's Upstart is still running until a reboot.
  Trusty's 'upstart' package ships a new 'initctl' binary that handles
  reloads only via the 'Reload' D-Bus method. Precise's Upstart doesn't
  support the 'Reload' D-Bus method though.

  Can Trusty's initctl binary be patched so that it falls back to the previous reload behavior if the Upstart version in use doesn't support the 'Reload' D-Bus method?
  Would you like me to open a new bug for this issue?

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