Hello,

We made some changes on our compute nodes in the “/etc/neutron/neutron.conf”. For example qpid_hostname. But nothing what effects the network infrastructure in the compute node.

To apply the changes I think we need to restart the “neutron-openvswitch-agent” service.

By restarting this service the VM gets disconnected for around one ping, the reason is the restart causes recreation of the int-br-bond0 and phy-br-bond0 interfaces:

ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=10 -- --may-exist add-br br-int

ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=10 -- set-fail-mode br-int secure

ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=10 -- --if-exists del-port br-int patch-tun

ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=10 -- --if-exists del-port br-int int-br-bond0

kernel: [73873.047999] device int-br-bond0 left promiscuous mode

ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=10 -- --if-exists del-port br-bond0 phy-br-bond0

kernel: [73873.086241] device phy-br-bond0 left promiscuous mode

ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=10 -- --may-exist add-port br-int int-br-bond0

kernel: [73873.287466] device int-br-bond0 entered promiscuous mode

ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=10 -- --may-exist add-port br-bond0 phy-br-bond0

Is there a way to apply this changes without loose pings?

Cheers

Chris