yahoo-eng-team team mailing list archive

[OpenStack Infra <1224967@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/50379
Committed: http://github.com/openstack/neutron/commit/b988984907d36ffbe593014c9433f2b0d26feb60
Submitter: Jenkins
Branch:    milestone-proposed

commit b988984907d36ffbe593014c9433f2b0d26feb60
Author: mathieu-rohon <mathieu.rohon@xxxxxxxxx>
Date:   Wed Oct 2 14:13:36 2013 +0200

    change port status only if port is bound to the good host
    
    if host is set in the rpc message update_device_up/down sent by the agent,
    the port status will be changed only if the port is bound to the host.
    
    Change-Id: I0e607c734fbebf0b69f83c3bbd3e25a9783672dc
    Closes-Bug: #1224967


** Changed in: neutron
       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/1224967

Title:
  port down after live migration

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  I'm using live-migration with devstack and ML2 plugin (the same error occurs with the OVS plugin)
  https://wiki.openstack.org/wiki/Devstack/LiveMigration

  First of all, I think there is a bug in nova :
  https://bugs.launchpad.net/nova/+bug/1224960

  I've proposed a patch attached to this bug to resolv it quickly.

  it seems that there is also something that goes wrong in neutron.
  after live-migrating a VM, the port is correctly created on the new host and the dataplane seems correct. But the port is still down in the port table, and the vif-type is "binding_failed" in ml2_port_bindings table

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1224967/+subscriptions