Swarm bays are failing after service failure logic added
Bug #1502329 reported by
Andrew Melton
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Logic was implemented to report back to heat when bay services failed to start. This logic performed a 'systemctl status X' for each service at the end of cloud-init. This will almost always fail because we have to start the bay services asynchronously and it is very likely they won't be started by the time the services are checked.
Changed in magnum: | |
milestone: | none → mitaka-1 |
Changed in magnum: | |
status: | Confirmed → Invalid |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/230639 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=156e315e98d fa7a0ebe759bb78 639c66eb0d8b77
Committed: https:/
Submitter: Jenkins
Branch: master
commit 156e315e98dfa7a 0ebe759bb78639c 66eb0d8b77
Author: Andrew Melton <email address hidden>
Date: Fri Oct 2 20:49:30 2015 +0000
Fix swarm bay failure reporting
The old method of detecting failures was very likely to fail in
many cases because it relied on all bay services being started by
the time cloud-init finished. This is a problem because the bay
services are started asynchronously and can take quite a while to
start.
The new method relies on systemd's OnFailure directive to kick off
specific service units when a failure is detected. Both the swarm
agent and manager have their own failure service so that we are
not overloading a single wait condition with multiple potential
failures.
Change-Id: I7ce4be567517fe 948dde0ac722599 6967196c9e8
Closes-bug: #1502329