Corosync service should be restarted on failover test
After the "killall" command the corosync service will be
in running state. That is why we should restart service
(but not start) to receive 0 exit code.
Change-Id: Ia46bbc31c6b4c49cdcc92047e1d51c6a5b2216de
Closes-Bug: 1637522
(cherry picked from commit f4348d5bb844ba33289536fa94a68f6602294b57)
Reviewed: https:/ /review. openstack. org/414446 /git.openstack. org/cgit/ openstack/ fuel-qa/ commit/ ?id=92fc50d1523 b037c6d1e106880 16a2d4072ef2ba
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit 92fc50d1523b037 c6d1e10688016a2 d4072ef2ba
Author: Dmitry Belyaninov <email address hidden>
Date: Wed Nov 9 12:20:50 2016 +0000
Corosync service should be restarted on failover test
After the "killall" command the corosync service will be
in running state. That is why we should restart service
(but not start) to receive 0 exit code.
Change-Id: Ia46bbc31c6b4c4 9cdcc92047e1d51 c6a5b2216de 3289536fa94a68f 6602294b57)
Closes-Bug: 1637522
(cherry picked from commit f4348d5bb844ba3