[system-tests] ha_corosync_stability_check: corosync service is not dead after killall

Bug #1637522 reported by Vladimir Khlyunev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Dmitry Belyaninov
Newton
Fix Committed
High
Dmitry Belyaninov

Bug Description

ha_neutron_destructive on snapshot #442 failed:
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.ha_neutron_destructive/110/testReport/(root)/ha_corosync_stability_check/ha_corosync_stability_check/

https://github.com/openstack/fuel-qa/blob/stable/mitaka/fuelweb_test/tests/tests_strength/test_failover_base.py#L1190

Scenario:
1 - Deploy HA cluster
2 - On controller kill corosync using "kilall -TERM corosync"
3 - Try start corosync using "service corosync start"

Result:
service is already running and "service corosync start" returns 1

root@node-1:~# service corosync restart
corosync stop/waiting
corosync start/running, process 12636
root@node-1:~# killall -TERM corosync
root@node-1:~# service corosync status
corosync start/running, process 12673
root@node-1:~# service corosync start
start: Job is already running: corosync

Changed in fuel:
status: New → Confirmed
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Dmitry Belyaninov (dbelyaninov)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-qa (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/395566

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-qa (stable/mitaka)

Reviewed: https://review.openstack.org/395566
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=f4348d5bb844ba33289536fa94a68f6602294b57
Submitter: Jenkins
Branch: stable/mitaka

commit f4348d5bb844ba33289536fa94a68f6602294b57
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: Ia46bbc31c6b4c49cdcc92047e1d51c6a5b2216de
    Closes-Bug: 1637522

tags: added: in-stable-mitaka
Revision history for this message
Dmitry Belyaninov (dbelyaninov) wrote :
Changed in fuel:
status: Confirmed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-qa (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/414446

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-qa (master)

Fix proposed to branch: master
Review: https://review.openstack.org/431344

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-qa (master)

Reviewed: https://review.openstack.org/431344
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=ee535ac5cfa59346cd1e87ea405927c6bc6d2e96
Submitter: Jenkins
Branch: master

commit ee535ac5cfa59346cd1e87ea405927c6bc6d2e96
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: Ia46bbc31c6b4c49cdcc92047e1d51c6a5b2216de
    Closes-Bug: 1637522
    (cherry picked from commit f4348d5bb844ba33289536fa94a68f6602294b57)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-qa (stable/newton)

Reviewed: https://review.openstack.org/414446
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=92fc50d1523b037c6d1e10688016a2d4072ef2ba
Submitter: Jenkins
Branch: stable/newton

commit 92fc50d1523b037c6d1e10688016a2d4072ef2ba
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: Ia46bbc31c6b4c49cdcc92047e1d51c6a5b2216de
    Closes-Bug: 1637522
    (cherry picked from commit f4348d5bb844ba33289536fa94a68f6602294b57)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/fuel-qa 11.0.0.0rc1

This issue was fixed in the openstack/fuel-qa 11.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.