docs - explicitly state that there should be NO second Fuel in the same network
Bug #1642744 reported by
Dmitry Sutyagin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Alexander Adamov |
Bug Description
We need to add a red notice that there should be only one Fuel server running in a given network set, otherwise various issues can occur. We know that there should be no second DHCP (cobbler), but that's not the only problem - second mcollective also causes unexpected behavior, etc etc. The best place is probably here - http://
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | Fuel Documentation Team (fuel-docs) → Evgeny Konstantinov (evkonstantinov) |
milestone: | none → 9.2 |
status: | Confirmed → Incomplete |
status: | Incomplete → Confirmed |
Changed in fuel: | |
assignee: | Evgeny Konstantinov (evkonstantinov) → Olga Gusarenko (ogusarenko) |
Changed in fuel: | |
assignee: | Olga Gusarenko (ogusarenko) → Alexander Adamov (aadamov) |
tags: | added: on-verification |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/399397
Review: https:/