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?
I'm currently testing Precise to Trusty upgrades and encountered - while troubleshooting bug http:// pad.lv/ 1301962 - this issue: Upstart0_ 6.Instance" doesn't exist
# initctl reload dbus
initctl: Method "Reload" with signature "" on interface "com.ubuntu.
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?