migrate vm, do not check neutron-openvswitch-agent status

[bailin.zhang]

when neutron-openvswitch-agent is offline. we can migrate VM to this node successfully.
but the port status is Down. and the binding:vif_type change into "binding_failed"

for example:
1. we have two compute nodes. named tecs110, tecs164
2. create a VM with ovs port at tecs110
3. stop neutron-openvswitch-agent of tecs164
4. migate the VM to tecs164
5. migate successfully, and check the port status.

Detail Operation process:
http://paste.openstack.org/show/493260/

[Sarafraj Singh (sarafraj-singh)]

Provide details of release/branch as where this bug was hit.

[bailin.zhang (bailin-zhang)]

find in kilo.But the codes of the last branch has this bug also.The process "select_destinations" do not check agent's status.

[Sarafraj Singh (sarafraj-singh)]

Might be related to https://bugs.launchpad.net/nova/+bug/1260440

[bailin.zhang (bailin-zhang)]

yes，the very same

> 在 2016年4月8日，23:29，Sarafraj Singh <email address hidden> 写道：
>
> Might be related to https://bugs.launchpad.net/nova/+bug/1260440
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1567232
>
> Title:
> migrate vm, do not check neutron-openvswitch-agent status
>
> Status in OpenStack Compute (nova):
> New
>
> Bug description:
> when neutron-openvswitch-agent is offline. we can migrate VM to this node successfully.
> but the port status is Down. and the binding:vif_type change into "binding_failed"
>
>
> for example:
> 1. we have two compute nodes. named tecs110, tecs164
> 2. create a VM with ovs port at tecs110
> 3. stop neutron-openvswitch-agent of tecs164
> 4. migate the VM to tecs164
> 5. migate successfully, and check the port status.
>
> Detail Operation process:
> http://paste.openstack.org/show/493260/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/1567232/+subscriptions