Pacemaker resource constraints cause API outage during maintenance
Bug #1802108 reported by
Lukas Bezdicka
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Critical
|
Lukas Bezdicka | ||
Bug Description
In more targeted testing of OSP10 minor update we found out there is an issue with way pacemaker services are created and how we defined the order constraints. We will have to provide fix for all the releases of OSP, but for OSP10 we probably will go with workaround I created and tested. Issue is pacemaker resource order constraints are kind Optional which means they do not apply on shutdown of pacemaker cluster on the node. This causes haproxy to be stopped before the VIP is migrated away from the node and subsequent APIs failure. Migration of VIPs will be applied in yum_update.sh script but we should also update the reboot documentation/
This bug applies to all minor update procedures.
| Changed in tripleo: | |
| milestone: | stein-2 → stein-3 |
Revision history for this message
| Juan Antonio Osorio Robles (juan-osorio-robles) wrote | #1 |
Revision history for this message
| Lukas Bezdicka (social-b) wrote | #2 |
Revision history for this message
| Lukas Bezdicka (social-b) wrote | #3 |
| Changed in tripleo: | |
| milestone: | stein-3 → stein-rc1 |
| Changed in tripleo: | |
| milestone: | stein-rc1 → train-1 |
| Changed in tripleo: | |
| milestone: | train-1 → train-2 |
| Changed in tripleo: | |
| milestone: | train-2 → train-3 |
| Changed in tripleo: | |
| milestone: | train-3 → train-rc1 |
Revision history for this message
| Lukas Bezdicka (social-b) wrote | #4 |
| Changed in tripleo: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Is this stillan issue?