NSX-mh: bad retry behaviour on controller connection issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Undecided
|
Unassigned | ||
Juno |
Fix Released
|
Undecided
|
Salvatore Orlando | ||
vmware-nsx |
Fix Released
|
High
|
Salvatore Orlando |
Bug Description
If the connection to a NSX-mh controller fails - for instance because there is a network issue or the controller is unreachable - the neutron plugin keeps retrying the connection to the same controller until it times out, whereas a correct behaviour would be to try to connect to the other controllers in the cluster.
The issue can be reproduced with the following steps:
1. Three Controllers in the cluster 10.25.56.
2. Neutron net-create dummy-1 from openstack cli
3. Vnc into controller-1, ifconfig eth0 down
4. Do neutron net-create dummy-2 from openstack cli
The API requests were forwarded to 10.25.56.223 originally. eth0 interface was shutdown on 10.25.56.223. But the requests continued to get forwarded to the same Controllers and timed out.
Changed in vmware-nsx: | |
importance: | Undecided → High |
Changed in neutron: | |
status: | New → Invalid |
Changed in vmware-nsx: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/214060
Review: https:/