Public bug reported:
[Impact]
On 16.04+ if you using upstart as your primary init system "enabled" services
that _only_ have upstart scripts fail to start with invoke-rc.d (with a default
policy). This is problematic as #DEBHELPER# tokens in maintscripts rely on
invoke-rc.d to start/stop services and fail to start services on installation.
[Test Case]
Boot into affected system with upstart as default init.
Try starting an 'upstart only' service with 'invoke-rc.d service start'.
It is expected this should work.
[Regression Potential]
14.04/upstart behavior is that invoke-rc.d works, and 16.04/systemd also has
invoke-rc.d start working with enabled services and default policy.
16.04/upstart should be the same.
** Affects: init-system-helpers (Ubuntu)
Importance: High
Assignee: Chris J Arges (arges)
Status: In Progress
** Affects: init-system-helpers (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: init-system-helpers (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Affects: init-system-helpers (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: init-system-helpers (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: init-system-helpers (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: init-system-helpers (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691474
Title:
invoke-rc.d service start fails on services with upstart-only scripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
