Primary controller role can be assigned to another controller during controllers scale up
Bug #1390397 reported by
Dima Shulyak
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Dima Shulyak | ||
5.1.x |
Won't Fix
|
High
|
Fuel Python (Deprecated) |
Bug Description
On first deployment primary_controller role is assigned to node with lowest uid in the array of nodes sended to deployment.
But in case you are scaling up controllers it is possible that newest controller will be with lowest uid, and therefore will be choosen as
primary_controller node.
We need to fix that in case we want to scale controllers, or it wont be possible to guarantee consistent behaviour
Changed in fuel: | |
status: | Invalid → Confirmed |
Changed in fuel: | |
status: | Confirmed → Triaged |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Dima Shulyak (dshulyak) |
Changed in fuel: | |
status: | Triaged → In Progress |
To post a comment you must log in.
imho the only viable option as to mark first controller added to the cluster as primary