service --status-all always reports upstart managed daemons as running
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lsb (Ubuntu) |
Fix Released
|
High
|
Steve Langasek | ||
| Trusty |
Fix Released
|
High
|
Steve Langasek | ||
Bug Description
[Impact]
This is a regression caused by the change to lsb-base that landed in -updates on the 12th of May:
lsb (4.1+Debian11ub
* Add 01-upstart-lsb from the upstart package and make
executing rc.d scripts no-op if there is an upstart
job for that script. (LP: #1273462)
-- Zhang Hua <email address hidden> Thu, 06 Aug 2015 11:11:16 -0500
This changed the behaviour of init.d scripts to pass through to the associated upstart configuration for process management, where packages ship both an upstart configuration and an init.d configuration.
This has a rather nasty side effect on 'service --status-all', which calls the 'status' method on all installed init.d scripts - this gets translated into:
status <service-name>
for upstart scripts, which correctly identifies the process as not running, but always returns a 0 return code. As a result, --status-all incorrectly identifies upstart processes as running even when they are not.
[Test Case]
1. On an installed trusty system, run this command to get a list of affected upstart jobs:
for job in $(initctl --system list | awk '/stop\/waiting/ {print $1}'); do if [ -x "/etc/init.d/$job" ]; then echo $job; fi; done
2. Check the status of this service in the output of service --status-all:
service --status-all 2>&1 | grep procps
3. Confirm that the service is shown as running, despite us knowing above that it is not:
[ + ] procps
4. Install the lsb-base package from trusty-proposed.
5. Check the status of this service again in the output of service --status-all:
service --status-all 2>&1 | grep procps
6. Confirm that the service is no longer shown as running:
[ - ] procps
[Regression Potential]
Minimal. This SRU updates the behavior of the lsb init script upstart diversion to implement LSB-compliant return values for the 'status' subcommand. It is possible this behavior change will differ from the original behavior of some init scripts, but that behavior was undefined.
| James Page (james-page) wrote | #1 |
| description: | updated |
| tags: | added: regression-update |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in lsb (Ubuntu): | |
| status: | New → Confirmed |
| James Page (james-page) wrote | #3 |
| Changed in lsb (Ubuntu): | |
| assignee: | nobody → Steve Langasek (vorlon) |
| importance: | Undecided → High |
| status: | Confirmed → Triaged |
| status: | Triaged → In Progress |
| Changed in lsb (Ubuntu Trusty): | |
| assignee: | nobody → Steve Langasek (vorlon) |
| importance: | Undecided → High |
| status: | New → In Progress |
| Changed in lsb (Ubuntu): | |
| status: | In Progress → Fix Committed |
| description: | updated |
| Martin Pitt (pitti) wrote Please test proposed package | #4 |
| Changed in lsb (Ubuntu Trusty): | |
| status: | In Progress → Fix Committed |
| tags: | added: verification-needed |
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in lsb (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Ubuntu Foundations Team Bug Bot (crichton) wrote [lsb/trusty] verification still needed | #6 |
| tags: | added: removal-candidate |
| Mathew Hodson (mhodson) wrote | #7 |
| tags: |
added: verification-done removed: removal-candidate verification-needed |
| description: | updated |
| Launchpad Janitor (janitor) wrote | #8 |
| Changed in lsb (Ubuntu Trusty): | |
| status: | Fix Committed → Fix Released |
| Martin Pitt (pitti) wrote Update Released | #9 |
Status changed to 'Confirmed' because the bug affects multiple users.