Pacemaker resources are stopped when corosync cluster lacks quorum, astute does not check amount of controllers
Bug #1419794 reported by
Igor Zinovik
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 1a0e360cd14bf35
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-
Actual result:
All pacemaker resources are stopped.
Workaround:
$ pcs property set no-quorum-
Impact:
deployment fails becase services and IP addresses are stopped/disabled.
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 |
tags: | added: system-test-added |
no longer affects: | fuel/6.0-updates |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/154099
Review: https:/