** Description changed:

  [Impact]
  
-  * Between upgrading upstart to trusty and rebooting: reload (initctl
+  * 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
+  * 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
+  * Minimal, this re-introduces a previously removed code-path as
  fallback when reload signal delivery fails.
  
  [Other Info]
-  
-  * original bug report below
+ 
+  * 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?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to