Pacemaker's resource do not propagate to the just joined node.
Bug #1582366 reported by
Andrii Petrenko
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Invalid
|
High
|
Fuel Library (Deprecated) | ||
| 6.1.x |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
During the outage we had an issue with 3 nodes (N1, N2, and N3) cluster configured:
1. N3 just joned pacemaker cluster.
2. all resources was present on nodes N1 and N2.
3. service status:
corosync up and running on all 3 nodes.
pacemaker up and running on all 3 nodes.
Please advise, how to diagnose fix that issue?
| tags: | added: customer-found support |
| summary: |
- Pacemaker's resoucre is not propagate to the just joined node. + Pacemaker's resource do not propagate to the just joined node. |
| Changed in mos: | |
| assignee: | nobody → Fuel Library (Deprecated) (fuel-library) |
| Changed in mos: | |
| importance: | Undecided → High |
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote | #1 |
| Changed in mos: | |
| status: | New → Incomplete |
Revision history for this message
| Dina Belova (dbelova) wrote | #2 |
| Changed in mos: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
Please provide logs, at least for corosync/