Public bug reported: Hi Team, I'm using Mitaka cluster driver for Hyper-V with OVS 2.5 Windows port. When I perform live migration, an instance loses network connection but succesfully migrates to another host. There was a bug in Liberty where ovs port had not been migrated to target hosts but now it is seems to be okay, ovs port is on target host but adds with errors.
vswitchd.log (migration time) https://paste.ubuntu.com/23510786/ nova-compute.log (migration time) https://paste.ubuntu.com/23510782/ nova.conf https://paste.ubuntu.com/23510815/ neutron-ovs-agent.conf https://paste.ubuntu.com/23510816/ If I execute the command (ovs-vsctl --timeout=120 -- --if-exists del- port 4b26fd63-e779-49c9-b419-ac2c53ef8c9a ....) logged in nova manually then I get network connection even without restarting the services. I can also restart hyper-v OVS and network connection becomes available. I've also logged OVS debug rpc (another try of migration) and it contains "protocols":"OpenFlow10","datapath_version":"<unknown>"} 2016-11-21T13:10:55.017Z|04642|netdevwindows|DBG|construct device 4b26fd63-e779-49c9-b419-ac2c53ef8c9a, ovstype: 0. 2016-11-21T13:10:55.017Z|04643|dpif|WARN|system@ovs-system: failed to add 4b26fd63-e779-49c9-b419-ac2c53ef8c9a as port: Invalid argument Another try: 2016-11-21T12:48:21.789Z|00444|dpif|DBG|system@ovs-system: device br-tun is on port 5 2016-11-21T12:48:21.789Z|00445|netlinksocket|DBG|received NAK error=0 (No such device) 2016-11-21T12:48:21.789Z|00446|netdevwindows|DBG|construct device 4b26fd63-e779-49c9-b419-ac2c53ef8c9a, ovstype: 0. 2016-11-21T12:48:21.789Z|00447|netlinksocket|DBG|received NAK error=0 (No such device) 2016-11-21T12:48:21.789Z|00448|netlink_socket|DBG|received NAK error=0 (Invalid argument) 2016-11-21T12:48:21.789Z|00449|dpif|WARN|system@ovs- system: failed to add 4b26fd63-e779-49c9-b419-ac2c53ef8c9a as port: Invalid argument https://paste.ubuntu.com/23511010/ ** Affects: nova Importance: Undecided Status: New ** Tags: hyper-v live-migration nova ovs -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1644122 Title: OVS port fails after hyper-v cluster live migration (Invalid argument) Status in OpenStack Compute (nova): New Bug description: Hi Team, I'm using Mitaka cluster driver for Hyper-V with OVS 2.5 Windows port. When I perform live migration, an instance loses network connection but succesfully migrates to another host. There was a bug in Liberty where ovs port had not been migrated to target hosts but now it is seems to be okay, ovs port is on target host but adds with errors. vswitchd.log (migration time) https://paste.ubuntu.com/23510786/ nova-compute.log (migration time) https://paste.ubuntu.com/23510782/ nova.conf https://paste.ubuntu.com/23510815/ neutron-ovs-agent.conf https://paste.ubuntu.com/23510816/ If I execute the command (ovs-vsctl --timeout=120 -- --if-exists del- port 4b26fd63-e779-49c9-b419-ac2c53ef8c9a ....) logged in nova manually then I get network connection even without restarting the services. I can also restart hyper-v OVS and network connection becomes available. I've also logged OVS debug rpc (another try of migration) and it contains "protocols":"OpenFlow10","datapath_version":"<unknown>"} 2016-11-21T13:10:55.017Z|04642|netdevwindows|DBG|construct device 4b26fd63-e779-49c9-b419-ac2c53ef8c9a, ovstype: 0. 2016-11-21T13:10:55.017Z|04643|dpif|WARN|system@ovs-system: failed to add 4b26fd63-e779-49c9-b419-ac2c53ef8c9a as port: Invalid argument Another try: 2016-11-21T12:48:21.789Z|00444|dpif|DBG|system@ovs- system: device br-tun is on port 5 2016-11-21T12:48:21.789Z|00445|netlinksocket|DBG|received NAK error=0 (No such device) 2016-11-21T12:48:21.789Z|00446|netdevwindows|DBG|construct device 4b26fd63-e779-49c9-b419-ac2c53ef8c9a, ovstype: 0. 2016-11-21T12:48:21.789Z|00447|netlinksocket|DBG|received NAK error=0 (No such device) 2016-11-21T12:48:21.789Z|00448|netlink_socket|DBG|received NAK error=0 (Invalid argument) 2016-11-21T12:48:21.789Z|00449|dpif|WARN|system @ovs-system: failed to add 4b26fd63-e779-49c9-b419-ac2c53ef8c9a as port: Invalid argument https://paste.ubuntu.com/23511010/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1644122/+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
