Open Stack

Hi Neil,

what's the status of the port after the migration? You might be hitting
[1] . See also the patch that fixes the issue [2]

If you wait a bit longer, is the host_id updated by Nova?

cheers,

Rossella

[1] https://bugs.launchpad.net/neutron/+bug/1439857
[2] https://review.openstack.org/#/c/163178/

On 05/14/2015 11:29 AM, Neil Jerram wrote:
> Hi all, this is about a problem I'm seeing with my Neutron ML2 mechanism
> driver [1].  I'm expecting to see an update_port_postcommit call to
> signal that the binding:host_id for a port is changing, but I don't see
> that.
> 
> The scenario is launching a new instance in a cluster with two compute
> hosts, where we've rigged things so that one of the compute hosts will
> always be chosen first, but libvirt isn't correctly configured there and
> hence the instance launching attempt will fail.  Then Nova tries to use
> the other compute host instead, and that mostly works - except that my
> mechanism driver still thinks that the new instance's port is still
> bound to the first compute host.
> 
> Is anyone aware of a known problem in this area (in Juno-level code), or
> where I could like to start pinning this down in more detail?
> 
> Many thanks,
>     Neil
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
>