vSwitch not being selected [closed]

asked 2019-01-17 10:23:25 +0300

This post is a wiki. Anyone with karma >75 is welcome to improve it.

I am trying to get a fresh install of OpenStack(Rocky)+Hyper-V up and working to try out. When it builds the new instance/vm in hyperv, it does not apply the vSwitch. I'm at a loss of what is the problem. Here is what the log looks like.

This is from neutrons server.log. Does that look correct? Openstack01 is my controller, not my compute node. "Servers" is my name of the Hyper-V Virtual Switch, should that be something else? If so what, and how do I find it out?

2019-01-20 03:45:37.549 129026 ERROR neutron.plugins.ml2.managers [req-c325b2f9-422a-4419-bb9f-7905c2857265 - - - - -] Failed to bind port 2a348c43-f996-4b67-a2e6-6174158e3557 on host openstack01 for vnic_type normal using segments [{'network_id': 'a0b42068-5ad7-4483-a36f-b62154d40561', 'segmentation_id': None, 'physical_network': u'Servers', 'id': '7dd36e8f-ff73-4763-b322-7e589b0995d5', 'network_type': u'flat'}]

This is the log off the hyperv server

2019-01-16 23:40:46.527 124 INFO neutron.common.config [-] Logging enabled!
2019-01-16 23:40:46.527 124 INFO neutron.common.config [-] C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\Scripts\neutron-hyperv-agent version 13.1.0.dev399
2019-01-16 23:40:46.558 124 INFO os_win.utils.network.networkutils [req-60bd73fb-04cc-4dce-8d7b-60dc980026ff - - - - -] WMI caching is disabled.
2019-01-16 23:40:47.574 124 INFO networking_hyperv.neutron.agent.hyperv_neutron_agent [req-60bd73fb-04cc-4dce-8d7b-60dc980026ff - - - - -] Agent initialized successfully, now running... 
2019-01-16 23:40:48.292 124 INFO networking_hyperv.neutron.agent.layer2 [req-60bd73fb-04cc-4dce-8d7b-60dc980026ff - - - - -] Adding port Network Adapter
2019-01-16 23:42:56.089 124 INFO neutron.agent.securitygroups_rpc [req-209c89e4-9d03-4f24-bff5-21c42f5d8f25 9b961f76dfba46438d08dd0deb7835e4 6df1cbc03e5b4aed94bd0fff75df7b29 - - -] Security group member updated ['0a4b090e-4d95-44b1-aed2-d75994088c92']
2019-01-17 00:10:46.363 124 INFO networking_hyperv.neutron.agent.layer2 [-] Hyper-V VM vNIC added: 88dfa1d2-a9b9-4060-8b7e-1f1e8a2fa4ae
2019-01-17 00:10:48.145 124 INFO networking_hyperv.neutron.agent.layer2 [req-60bd73fb-04cc-4dce-8d7b-60dc980026ff - - - - -] Adding port 88dfa1d2-a9b9-4060-8b7e-1f1e8a2fa4ae
2019-01-17 01:16:46.360 476 INFO neutron.common.config [-] Logging enabled!
2019-01-17 01:16:46.376 476 INFO neutron.common.config [-] C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\Scripts\neutron-hyperv-agent version 13.1.0.dev399
2019-01-17 01:16:46.376 476 DEBUG neutron.common.config [-] command line: C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\Scripts\neutron-hyperv-agent --config-file C:\Program Files\Cloudbase Solutions\OpenStack\Nova\etc\neutron_hyperv_agent.conf setup_logging C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\lib\site-packages\neutron\common\config.py:103
2019-01-17 01:16:46.407 476 INFO os_win.utils.network.networkutils [req-ea999013-0644-4a44-b6d3-765dec049fde - - - - -] WMI caching is disabled.
2019-01-17 01:16:47.001 476 DEBUG neutron.agent.securitygroups_rpc [req-ea999013-0644-4a44-b6d3-765dec049fde - - - - -] Init firewall settings (driver=hyperv) init_firewall C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\lib\site-packages\neutron\agent\securitygroups_rpc.py:76
2019-01-17 01:16:47.126 476 DEBUG neutron.api.rpc.callbacks.resource_manager [req-ea999013-0644-4a44-b6d3-765dec049fde - - - - -] Registering callback for Trunk register C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\lib\site-packages\neutron\api\rpc\callbacks\resource_manager.py:64
2019-01-17 01:16:47.141 476 DEBUG neutron.api.rpc.callbacks.resource_manager [req-ea999013-0644-4a44-b6d3-765dec049fde - - - - -] Registering callback for SubPort register C:\Program Files\Cloudbase Solutions\OpenStack\Nova\Python\lib\site-packages\neutron\api\rpc\callbacks\resource_manager.py:64
2019-01-17 01:16:47.563 476 INFO networking_hyperv.neutron.agent.hyperv_neutron_agent [req-ea999013-0644-4a44-b6d3-765dec049fde - - - - -] Agent initialized successfully, now running... 
2019-01-17 01:16:47.657 476 DEBUG ...

(more)

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by johnwc
close date 2019-01-24 23:29:54.494659

add a comment

0

answered 2019-01-18 09:15:26 +0300

lpetrut
206 ●3 ●3

Hi,

Judging by the logs, the agent could not fetch the port details from the neutron server as there's no binding for this host:

Missing port_id from device details: 88dfa1d2-a9b9-4060-8b7e-1f1e8a2fa4ae. Details: {'device': '88dfa1d2-a9b9-4060-8b7e-1f1e8a2fa4ae', 'no_active_binding': True}

There are two main reasons why this could happen: either you haven't installed networking-hyperv on your neutron server, or you're using an unsupported network type. Be aware that this agent only supports flat or vlan networks. For anything else, you may use the ovs neutron agent.

Regards, Lucian

edit flag offensive delete link

Comments

Well, I originally tried to get ovs working and just couldn't figure it out. So I updated the configs to be setup as a provider network only. Doing this, did I need to also rebuild the neutron DB? Is it thinking that ovs is still setup in the DB, and that is what it's confused about?

johnwc ( 2019-01-18 09:52:59 +0300 )edit

I have networking-hyperv installed on both controller and compute node, and I only have flat and vlan set. I will update my question with config settings. How does the neutron server determine what the "port_id" is? What is the magic that I'm not seeing here?

johnwc ( 2019-01-20 12:37:09 +0300 )edit

Anything useful in the neutron server logs? It should tell us why it could not bind the port. It's something like this: the neutron agent running on the compute host sees the port, asks neutron server about it, which replies that it couldn't bind the port on that host.

lpetrut ( 2019-01-29 11:16:56 +0300 )edit

You don't have to rebuild the DB.

lpetrut ( 2019-01-29 11:17:40 +0300 )edit

add a comment

0

answered 2019-01-24 23:29:19 +0300

johnwc
1 ●2 ●3 ●3

Closing this and moving it to a new thread, as I am not seeing this error anymore when using packstack to install. But, still not getting vSwitch assigned to NIC.

edit flag offensive delete link

add a comment

vSwitch not being selected [closed]

Closed for the following reason the question is answered, right answer was accepted by johnwc
close date 2019-01-24 23:29:54.494659

2 answers

Comments

Question Tools

Stats

Related questions

vSwitch not being selected [closed] edit

Closed for the following reason the question is answered, right answer was accepted by johnwc close date 2019-01-24 23:29:54.494659

2 answers

Comments

Question Tools

Stats

Related questions

vSwitch not being selected [closed]

Closed for the following reason the question is answered, right answer was accepted by johnwc
close date 2019-01-24 23:29:54.494659