New Question

Openstack nic not getting attached to vm switch

asked 2019-10-30 22:50:48 +0300

timco64 gravatar image

updated 2019-11-14 15:35:27 +0300

I'm using kolla-ansible rocky branch with source containers to deploy openstack. I'm running the controller as a vm on top of my hyper-v compute host. I have a vlan subnet created but the vm's nic does not get attached to a switch. I'm using windows 2016 server on the hyper-v side.

This is the relevent log from my hyperv-neutron agent.

2019-10-30 15:44:37.697 7276 DEBUG networking_hyperv.neutron.agent.layer2 [req-019bb2af-11d1-4346-8765-658f7e53d76a - - - - -] Agent loop has new devices! _work C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\lib\site-packages\networking_hyperv\neutron\agent\
2019-10-30 15:44:38.056 7276 INFO networking_hyperv.neutron.agent.layer2 [req-019bb2af-11d1-4346-8765-658f7e53d76a - - - - -] Adding port 27b64897-28b5-4177-af65-157f1f103d35
2019-10-30 15:44:38.056 7276 DEBUG networking_hyperv.neutron.agent.layer2 [req-019bb2af-11d1-4346-8765-658f7e53d76a - - - - -] Missing port_id from device details: 27b64897-28b5-4177-af65-157f1f103d35. Details: {'device': '27b64897-28b5-4177-af65-157f1f103d35', 'no_active_binding': True} _treat_devices_added C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\lib\site-packages\networking_hyperv\neutron\agent\
2019-10-30 15:44:38.072 7276 DEBUG networking_hyperv.neutron.agent.layer2 [req-019bb2af-11d1-4346-8765-658f7e53d76a - - - - -] Remove the port from added ports set, so it doesn't get reprocessed. _treat_devices_added C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\lib\site-packages\networking_hyperv\neutron\agent\

I read a bit and some suggest this is because the neutron-server does not have the networking-hyperv package. Well mine does and it's version 5.0.0 but the package on my hyperv server is I used this installer to install the openstack hyperv bits

Here are the neutron server logs in debug mode

2019-11-14 08:17:39.373 28 DEBUG neutron.db.db_base_plugin_common [req-ca3e8550-af53-4152-8999-530c3169ee77 8c5f2b9d28c6406f829719bc79fb6268 0e170d3f44bd48ebb9a93123452a2928 - default default] Allocated IP (f247d20a-56e8-4ac5-be99-b3f6015032bc/208d961c-b476-4b19-842b-2746aaf717c9/9cc09af2-d7f1-4534-8cb8-e84a27cf7a77) _store_ip_allocation /var/lib/kolla/venv/lib/python2.7/site-packages/neutron/db/
2019-11-14 08:17:39.619 28 DEBUG neutron.db.provisioning_blocks [req-ca3e8550-af53-4152-8999-530c3169ee77 8c5f2b9d28c6406f829719bc79fb6268 0e170d3f44bd48ebb9a93123452a2928 - default default] Transition to ACTIVE for port object 9cc09af2-d7f1-4534-8cb8-e84a27cf7a77 will not be triggered until provisioned by entity DHCP. add_provisioning_component /var/lib/kolla/venv/lib/python2.7/site-packages/neutron/db/
2019-11-14 08:17:39.830 28 DEBUG neutron.api.rpc.handlers.resources_rpc [req-ca3e8550-af53-4152-8999-530c3169ee77 8c5f2b9d28c6406f829719bc79fb6268 0e170d3f44bd48ebb9a93123452a2928 - - -] Pushing event updated for resources: {'Port': ['ID=9cc09af2-d7f1-4534-8cb8-e84a27cf7a77,revision_number=1']} push /var/lib/kolla/venv/lib/python2.7/site-packages/neutron/api/rpc/handlers/
2019-11-14 08:17:40.607 28 DEBUG neutron.notifiers.nova [req-9f1eecb8-7f1b-4aad-83ed-2ddf2b6dfaab efeb14094ce14997aafeaf9764a4f44e 9d09538f8c0e47be85843674bf7c3767 - default default] Ignoring state change previous_port_status: DOWN current_port_status: DOWN port_id 9cc09af2-d7f1-4534-8cb8-e84a27cf7a77 record_port_status_changed /var/lib/kolla/venv/lib/python2.7/site-packages/neutron/notifiers/
2019-11-14 08:17:40.633 28 DEBUG neutron.db.provisioning_blocks [req-9f1eecb8-7f1b-4aad-83ed-2ddf2b6dfaab efeb14094ce14997aafeaf9764a4f44e 9d09538f8c0e47be85843674bf7c3767 - default default] Transition to ACTIVE for port object 9cc09af2-d7f1-4534-8cb8-e84a27cf7a77 will not be triggered until provisioned by entity L2. add_provisioning_component /var/lib/kolla/venv/lib/python2.7/site-packages/neutron/db/
2019-11-14 08:17:40.778 28 DEBUG neutron.api.rpc.handlers.resources_rpc [req-9f1eecb8-7f1b-4aad-83ed-2ddf2b6dfaab efeb14094ce14997aafeaf9764a4f44e 9d09538f8c0e47be85843674bf7c3767 - - -] Pushing event updated for resources: {'Port': ['ID=9cc09af2-d7f1-4534-8cb8-e84a27cf7a77,revision_number=2']} push /var/lib/kolla ...
edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2019-11-04 11:59:37 +0300

lpetrut gravatar image


Make sure to also enable the hyperv ml2 plugin as described here:

Now that I think of it, we'll probably want to move that section to the "prerequisites" page.

Regards, Lucian

edit flag offensive delete link more


My ml2_conf.ini has hyperv enabled and the networking-hyperv package is installed on the neutron-server. VM still does not get a hyper-v switch set.

timco64 gravatar imagetimco64 ( 2019-11-11 16:08:20 +0300 )edit

I suggest enabling debug mode for the neutron services (hyper-v as well as neutron server) and check the logs. You may search by port id, most probably this will get us to the cause of the port binding failures.

lpetrut gravatar imagelpetrut ( 2019-11-12 17:59:10 +0300 )edit

I have attached the relevant logs. Thanks for your help.

timco64 gravatar imagetimco64 ( 2019-11-14 15:35:56 +0300 )edit

Thanks for the logs, those helped me find the issue. I sent a fix and by next week we should have updated MSIs as well as a new networking-hyperv package that you may install manually. To be honest, we've been mostly focusing on the OVS neutron agent and this issue has somehow slipped.

lpetrut gravatar imagelpetrut ( 2019-11-14 19:44:37 +0300 )edit

Thanks, I'll explore the OVS agent until then.

timco64 gravatar imagetimco64 ( 2019-11-15 20:42:00 +0300 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2019-10-30 22:50:48 +0300

Seen: 513 times

Last updated: Nov 14 '19