MOS7, MU3, adding mongoDB node failed
Bug #1606158 reported by
ZHI BING WANG
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
ZHI BING WANG |
Bug Description
If the primary mongoDB role node got removed from the ENV, then added it back as MongoDB role, Fuel still considers it as the primary MongoDB node.
During deployment, it tries to create a new replica set and get the other mongo nodes to join. However, those nodes are still in old replica set, so the operation fails and the deployment fail.
To reproduce
create an ENV with Ceilometer and specify 3 Mongo nodes
Delete the primary Mongo node
Then add it back to the ENV
The deployment will fail
tags: | added: ceilometer customer-found mongo |
Changed in fuel: | |
assignee: | nobody → MOS Maintenance (mos-maintenance) |
milestone: | none → 7.0-updates |
Changed in fuel: | |
assignee: | MOS Maintenance (mos-maintenance) → Anton Chevychalov (achevychalov) |
Changed in fuel: | |
assignee: | Anton Chevychalov (achevychalov) → ZHI BING WANG (zwang) |
Changed in fuel: | |
importance: | Undecided → Medium |
Changed in fuel: | |
status: | Incomplete → Confirmed |
status: | Confirmed → Incomplete |
To post a comment you must log in.
Unable to reproduce bug in test environment. Is MOS version in that bug correct? Please check it.