Default values for WAIT_STATE are wrong in the upstart wait-for-state job
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Trusty |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
In Ubuntu 14.04, the wait-for-state job uses the env vars WAIT_STATE=
However, according to the upstart cookbook, the desired states for a already started/stopped job are 'start/running' and 'stop/waiting'. Maybe a misunderstood has occurred was the meaning of signals was job states (for example, after a job reaches the start/running state, it emits the started signal).
The strange thing is that the waiting/running wait states were proposed at the first implementations of this job, and not the stopped/started states: https:/
This bug can make some developers to write upstart jobs that return errors (like the GlusterFS developers, that forgot the WAIT_STATE=
References:
- http://
- http://
- https:/
I'm attaching a patch too.
tags: | added: trusty |
Changed in upstart (Ubuntu): | |
importance: | Undecided → Medium |
status: | Incomplete → Confirmed |
The attachment "wait-for- state.conf. patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]