Two out of three heat-engine services are not started in HA mode
Bug #1386318 reported by
Sergey Kraynev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Igor Yozhikov |
Bug Description
In HA mode we have three controllers with only one controller with started heat-engine (via corosync and pacemaker ).
We wants to check how three heat-engine work without corosync.
tags: | added: heat |
description: | updated |
Changed in fuel: | |
milestone: | none → 6.0 |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Sergey Kraynev (skraynev) → nobody |
assignee: | nobody → Anastasia Kuznetsova (akuznetsova) |
Changed in fuel: | |
assignee: | nobody → Igor Yozhikov (iyozhikov) |
Changed in fuel: | |
importance: | Medium → High |
Changed in fuel: | |
status: | Confirmed → Fix Committed |
tags: | added: on-verification |
To post a comment you must log in.
Now we have only one started heat-engine by "design", this comes from pacemaker heat manifests:
class pacemaker_ wrappers: :heat inherits heat::engine { stickiness' => '1'
$primitive_type = 'heat-engine'
...
$metadata = {
'resource-
}
We need to run all heat-engines as services like heat-api