Of course.
I actually only know two examples:
- mounting-glusterfs.conf: The glusterfs-client package uses the command
"wait-for-state WAIT_FOR=static-network-up WAITER=mounting-glusterfs" without
passing "WAIT_STATE=running";
- So, this command doesn't works;
- See: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1465382 and
https://bugzilla.redhat.com/show_bug.cgi?id=1231983;
- nova-compute.conf: The nova-compute package uses the comand wait-for-
state, but passes the WAIT_STATE=running option ("running", in my
opinion, should be the default instead of "started"):
# If libvirt-bin is installed, always wait for it to start first
if status libvirt-bin; then
start wait-for-state WAIT_FOR=libvirt-bin WAIT_STATE=running
WAITER=nova-compute
fi
So, it works.
Again, in the link http://upstart.ubuntu.com/cookbook/#job-states, we
can sse that 'start/running' and 'stop/waiting' are the correct states,
and not the 'start/started' and 'stop/stopped'.
** Bug watch added: Red Hat Bugzilla #1231983
https://bugzilla.redhat.com/show_bug.cgi?id=1231983
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465386
Title:
Default values for WAIT_STATE are wrong in the upstart wait-for-state
job
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1465386/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
