Always wait for keystone haproxy backends then deploying a primary controller
Bug #1394140 reported by
Bogdan Dobrelya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Bogdan Dobrelya | ||
5.1.x |
Fix Released
|
Critical
|
Bogdan Dobrelya | ||
6.0.x |
Fix Released
|
Critical
|
Bogdan Dobrelya |
Bug Description
We wait for haproxy backend only for nova-network case, but neutron case *does* rely on keystone as well.
If we don't wait for keystone haproxy backends, we could end up with neutron net-list failures
To post a comment you must log in.
Raised to critical due to many duplicates (i.e. bugs with neutron net-list failures or glance wasn't properly installed failures could be related to this one)