It is necessary to forbid adding MongoDB nodes if there are deployed nodes already
Bug #1310519 reported by
Alexander Kislitsky
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Julia Aranovich |
Bug Description
During the deployment MongoDB nodes are configured as primary-secondary servers.
In case of adding MongoDB nodes into current configuration we must reconfigure OpenStack and redeploy MongoDB nodes. Reconfiguration and redeployment cause data loosing.
So now we should forbid adding MongoDB nodes if there are already deployed nodes in UI.
Changed in fuel: | |
assignee: | Fuel UI Team (fuel-ui) → Julia Aranovich (jkirnosova) |
status: | Confirmed → In Progress |
To post a comment you must log in.
Fix is provided in https:/ /review. openstack. org/#/c/ 89327/ request.