Pacemaker has wrong configuration on a controller after deletion other controllers from HA cluster

Bug #1450399 reported by Dennis Dmitriev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
High
Fuel Library (Deprecated)

Bug Description

Scenario:
    1) Create HA cluster (Ubuntu/Centos) : 3 controllers, 1 compute;
    2) Deploy cluster;
    3) Check that OSTF passed successfully, `pcs status` example: http://paste.openstack.org/show/213411/;
    4) Delete any two controllers from the cluster via Nailgun API/UI/CLI
    5) Run OSTF , check `pcs status` on the remaining controller

Expected resuld: OSTF passed on step 5; `pcs status` shows that DC has a quorum and there are running VIPs and other resources.

Actual result: `pcs status` on the remaining controller shows that the controller has no quorum (example: http://paste.openstack.org/show/213412/):
"Current DC: node-1.test.domain.local (1) - partition WITHOUT quorum"

, and it is waiting for other controllers that have been deleted:
Online: [ node-1.test.domain.local ]
OFFLINE: [ node-2.test.domain.local node-3.test.domain.local ]

As the result: cluster is in the non-operational state because pacemaker stopped all resources on the remaining controller.

Pacemaker should be re-configured after controller deletion.

Tags: pacemaker
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

ISO version: {"build_id": "2015-04-29_07-55-19", "build_number": "361", "release_versions": {"2014.2.2-6.1": {"VERSION": {"build_id": "2015-04-29_07-55-19", "build_number": "361", "api": "1.0", "fuel-library_sha": "0e5b82d24853304befb22145ac4aaf3545d295e1", "nailgun_sha": "e660b1c09d7d4d07bdd48d424ce9aed3b6facd6e", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "8cd6cf575d3c101dee1032abb6877dfa8487e077", "astute_sha": "04ebab96d57b0e8acbf2d7f3ba05e4fbf31b741e", "fuel-ostf_sha": "b38602c841deaa03ddffc95c02f319360462cbe3", "release": "6.1", "fuelmain_sha": "ee112acfdd0f9017ef40be53e8e51bb5c429e97c"}}}, "auth_required": true, "api": "1.0", "fuel-library_sha": "0e5b82d24853304befb22145ac4aaf3545d295e1", "nailgun_sha": "e660b1c09d7d4d07bdd48d424ce9aed3b6facd6e", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "8cd6cf575d3c101dee1032abb6877dfa8487e077", "astute_sha": "04ebab96d57b0e8acbf2d7f3ba05e4fbf31b741e", "fuel-ostf_sha": "b38602c841deaa03ddffc95c02f319360462cbe3", "release": "6.1", "fuelmain_sha": "ee112acfdd0f9017ef40be53e8e51bb5c429e97c"}

description: updated
Changed in fuel:
importance: Undecided → High
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.