[Yahoo-eng-team] [Bug 1485883] Re: NSX-mh: bad retry behaviour on controller connection issues
** Changed in: vmware-nsx Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1485883 Title: NSX-mh: bad retry behaviour on controller connection issues Status in neutron: Invalid Status in neutron juno series: Fix Released Status in vmware-nsx: Fix Released 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.223,10.25.101.133,10.25.56.222 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. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1485883/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1485883] Re: NSX-mh: bad retry behaviour on controller connection issues
** Changed in: neutron/juno Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1485883 Title: NSX-mh: bad retry behaviour on controller connection issues Status in neutron: Invalid Status in neutron juno series: Fix Released Status in vmware-nsx: Fix Committed 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.223,10.25.101.133,10.25.56.222 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. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1485883/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1485883] Re: NSX-mh: bad retry behaviour on controller connection issues
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Status: New => Invalid ** Also affects: neutron/juno Importance: Undecided Status: New ** Changed in: neutron/juno Status: New => Fix Committed ** Changed in: neutron/juno Assignee: (unassigned) => Salvatore Orlando (salvatore-orlando) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1485883 Title: NSX-mh: bad retry behaviour on controller connection issues Status in neutron: Invalid Status in neutron juno series: Fix Committed Status in vmware-nsx: Fix Committed 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.223,10.25.101.133,10.25.56.222 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. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1485883/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
