Pacemaker resources are stopped when corosync cluster lacks quorum, astute does not check amount of controllers

Bug #1419794 reported by Igor Zinovik
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Dmitry Ilyin
6.0.x
Invalid
Undecided
Unassigned

Bug Description

After commit 1a0e360cd14bf3511bc8e390b54ee2530399d12c was merged in fuel-library/
repository astute changes pacemakers quorum policy to 'stop'. This means that when pacemaker
cluster does not have quorum (1 or 2 controllers) it will stop all pacemaker resources.

Expected result:
Cluster without quorum has no-quorum-policy=ignore

Actual result:
All pacemaker resources are stopped.

Workaround:
$ pcs property set no-quorum-policy=ignore

Impact:
deployment fails becase services and IP addresses are stopped/disabled.

Igor Zinovik (izinovik)
summary: - Fuel stops all pacemaker resources when corosync cluster lacks quorum
+ Pacemaker resources are stopped when corosync cluster lacks quorum
summary: - Pacemaker resources are stopped when corosync cluster lacks quorum
+ Pacemaker resources are stopped when corosync cluster lacks quorum,
+ astute does not check amount of controllers
Changed in fuel:
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

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

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/154099
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=33f204d36181566649cd09a8b2ef3c8f8084048f
Submitter: Jenkins
Branch: master

commit 33f204d36181566649cd09a8b2ef3c8f8084048f
Author: Dmitry Ilyin <email address hidden>
Date: Mon Feb 9 19:07:48 2015 +0300

    Rewrite enable_quorum task

    * Set policy to stop only in there are motre then 2 controllers
    * Add retries and timeouts

    Change-Id: I70d734dfde7c2a56b91d6f2701a159d3cff535cb
    Closes-Bug: 1419794

Changed in fuel:
status: In Progress → Fix Committed
tags: added: system-test-added
no longer affects: fuel/6.0-updates
Revision history for this message
Anastasia Palkina (apalkina) wrote :

Verified on ISO #156

"build_id": "2015-03-02_22-54-44", "ostf_sha": "103d6cf6badd57b791cfaf4310ec8bd81c7a8a46", "build_number": "156", "release_versions": {"2014.2-6.1": {"VERSION": {"build_id": "2015-03-02_22-54-44", "ostf_sha": "103d6cf6badd57b791cfaf4310ec8bd81c7a8a46", "build_number": "156", "api": "1.0", "nailgun_sha": "5da9e633204fa0affb86208ea2989500881f8ec2", "production": "docker", "python-fuelclient_sha": "3ebfa9c14a192d0298ff787526bf990055a23694", "astute_sha": "1be5b9b827f512d740fe907c7ff72486d4030938", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "baf24424a4e056c6753913de5f8c94851903f718", "fuellib_sha": "92d7c3021d573952b65cd5705a6c690cd24d9de3"}}}, "auth_required": true, "api": "1.0", "nailgun_sha": "5da9e633204fa0affb86208ea2989500881f8ec2", "production": "docker", "python-fuelclient_sha": "3ebfa9c14a192d0298ff787526bf990055a23694", "astute_sha": "1be5b9b827f512d740fe907c7ff72486d4030938", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "baf24424a4e056c6753913de5f8c94851903f718", "fuellib_sha": "92d7c3021d573952b65cd5705a6c690cd24d9de3"

Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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