[ops][nova][neutron] Proper way to migrate instances between nodes with different ML2 agents types
antoine.millet at enix.fr
Fri Nov 8 15:53:27 UTC 2019
Thank you for your answer!
> 1. Is Neutron fully upgraded to Rocky and exposing the "Port
> Extended" (binding-extended) extension? Nova uses that to determine
> neutron is new enough to create an inactive port binding for the
> host prior to starting the live migration.
I'm not sure how to test that but my neutron components are all
upgraded to rocky / 13.0.4.
> 2. Are your nova-compute services all upgraded to at least Rocky and
> reporting version >=35 in the services table in the cell1 DB? 
I can confirm that.
> 3. Do you have [compute]/upgrade_levels RPC pinned to anything below
> Rocky? Or is that configured to "auto"?
All the upgrade_levels on compute are pinned to auto (control plane and
> If that's all working properly, you should see this DEBUG log message
> the source host during live migration .
I can actually see this message on the nova-compute logs:
2019-11-08 16:34:18.599 3995 DEBUG nova.virt.libvirt.migration [-]
[instance: 3dbf401b-19bf-4342-a04e-6ac9cff99efe] Updating guest XML
with vif config: <interface type="bridge">
And here is the problem at the same time at the destination:
2019-11-08 15:34:23.720 4434 ERROR os_vif AgentError: Error during
following call to agent: ['ovs-vsctl', '--timeout=120', '--', '--if-
exists', 'del-port', u'br-int', u'qvoea312a58-2e']
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: This is a digitally signed message part
More information about the openstack-discuss