invoke-rc.d service start fails on services with upstart-only scripts

Bug #1691474 reported by Chris J Arges on 2017-05-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
init-system-helpers (Ubuntu)
High
Chris J Arges
Xenial
Undecided
Unassigned
Yakkety
Undecided
Unassigned
Zesty
Undecided
Unassigned

Bug Description

[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.

Chris J Arges (arges) wrote :
tags: added: patch
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers