control-node didn't receive configuration from ifmap
Bug #1588939 reported by
Hampapur Ajay
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
New
|
Undecided
|
Unassigned | ||
Bug Description
On a 5 controller node configuration following was observed. Details will be added to bug as discovered.
control-node on controller #3 was connected to ifmap on controller #4
controller #4 (VM) died cold due to out-of-memory issue on kernel
control-node connected to ifmap on controller #5. However it didn't receive configuration for self and published to discovery of itself as down (no config for self)
A few hours later this was discovered and control-node was restarted on controller #3.
This time it re-connected to ifmap on controller #5 and it got config for itself and published to discovery as UP
| information type: | Proprietary → Public |
To post a comment you must log in.
