New Question
0

OpenV switch neutron error

asked 2019-11-21 14:23:24 +0300

renjith2cr gravatar image

updated 2019-11-21 15:04:48 +0300

Deployed open stack Rocky with hyper V. We are using OVS and flat network. Nova and neutron agents are up but Instance creation is failing with below error.

Error: Failed to perform requested operation on instance "win", the instance has an error status: Please try again later [Error: Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance 8d262f0e-a851-4cd1-84c5-422e9d532fc2.].

neutron-dhcp-agent.log

2019-11-21 17:28:25.226 5959 INFO neutron.agent.dhcp.agent [-] Trigger reload_allocations for port admin_state_up=True, allowed_address_pairs=[], binding:host_id=COMPUTE, binding:profile=, binding:vif_details=, binding:vif_type=binding_failed, binding:vnic_type=normal, created_at=2019-11-21T11:58:19Z, description=, device_id=8d262f0e-a851-4cd1-84c5-422e9d532fc2, device_owner=compute:nova, extra_dhcp_opts=[], fixed_ips=[{u'subnet_id': u'0df91235-cf72-40ef-a083-b46c5e218b77', u'ip_address': u'IP'}], id=c61f7a4a-1bb2-42f4-935f-8c3ae3f41c4a, mac_address=fa:16:3e:0d:44:aa, name=, network_id=911f6654-82b9-4a9f-9b38-6eed9af05bb0, port_security_enabled=True, project_id=216c81f417014f44b38276cc2e5c1189, revision_number=3, security_groups=[u'793e1067-07d9-4882-850a-fe6cd4b2893a'], **status=DOWN**, tags=[], tenant_id=216c81f417014f44b38276cc2e5c1189, updated_at=2019-11-21T11:58:24Z

neutron-ovs-agent.log

2019-11-21 17:45:37.960 7736 ERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor unix:C:\ProgramData\openvswitch\db.sock Bridge name --format=json]: None
2019-11-21 17:46:08.101 7736 ERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor unix:C:\ProgramData\openvswitch\db.sock Bridge name --format=json]: 2019-11-21T12:16:08Z|00001|util|EMER|failed to connect or listen to "unix:C:\ProgramData\openvswitch\db.sock" (Unknown error)
2019-11-21 17:46:08.101 7736 ERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor unix:C:\ProgramData\openvswitch\db.sock Bridge name --format=json]: None
2019-11-21 17:46:38.241 7736 ERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor unix:C:\ProgramData\openvswitch\db.sock Bridge name --format=json]: 2019-11-21T12:16:38Z|00001|util|EMER|failed to connect or listen to "unix:C:\ProgramData\openvswitch\db.sock" (Unknown error)
2019-11-21 17:46:38.241 7736 ERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor unix:C:\ProgramData\openvswitch\db.sock Bridge name --format=json]: None

neutronovsagent.conf

[DEFAULT]
control_exchange=neutron
transport_url=rabbit://user:password@controller
log_dir=D:\OpenStack\Log\
log_file=neutron-ovs-agent.log

[AGENT]
enable_metrics_collection=false
tunnel_types=vxlan

[SECURITYGROUP]
firewall_driver=openvswitch
enable_security_group=true

[ovs]
local_ip=IP
integration_bridge=br-int
tenant_network_type=vxlan
ovsdb_connection=unix:C:\ProgramData\openvswitch\db.sock
enable_tunneling=true
tunnel_bridge=br-tun

OVS Details

PS C:\Users\Administrator> ovs-vsctl.exe show
e68a7179-3667-4c20-9eed-7ce879501ca8
    Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
        Port "vxlan-0a962333"
            Interface "vxlan-0a962333"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.150.35.29", out_key=flow, remote_ip="10.150.35.51"}
    Bridge br-data
        Port br-data
            Interface br-data
                type: internal
        Port "SIOM Port 1"
            Interface "SIOM Port 1"
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}

Controller

# ovs-vsctl show
44425bcb-cf92-4a6b-84e8-4be1a9ac3fe5
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-provider
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure ...
(more)
edit retag flag offensive close merge delete

2 answers

Sort by » oldest newest most voted
0

answered 2019-12-05 13:33:57 +0300

renjith2cr gravatar image

updated 2019-12-05 13:52:23 +0300

I have fixed the error by adding below line on neutronovsagent.conf

bridge_mappings=provider:br-provider

Now I'm able to provision VMs in both Provider and self network.

edit flag offensive delete link more
0

answered 2019-11-21 15:14:29 +0300

lpetrut gravatar image

updated 2019-11-21 15:32:30 +0300

Hi,

ovsdb is probably not configured to listen to that pipe. In most cases, ovsdb listens to :6640. You may set the following in your neutron-ovs-agent.conf:

[ovs]
ovsdb_connection = "tcp:127.0.0.1:6640"

Ensure that ovsdb listens to that port by issuing the following:

ovs-appctl -t ovsdb-server ovsdb-server/add-remote ptcp:6640:127.0.0.1

Alternatively, you may use the following if you want to stick to unix sockets (ovs is using named pipes on Windows behind the scenes as Unix sockets are relatively new on Windows):

ovs-appctl -t ovsdb-server ovsdb-server/add-remote punix:C:\ProgramData\openvswitch\db.sock

Regards, Lucian

edit flag offensive delete link more

Comments

@Lucian Thanks for the input. I have included the lines to neutron_ovs_agent.conf and restarted the services. But the second command (for ensuring ) not returned anything. The same port is litsening in controller side. tcp 0 0 127.0.0.1:6640 0.0.0.0:* LISTEN

renjith2cr gravatar imagerenjith2cr ( 2019-11-21 16:31:08 +0300 )edit

Getting the same errors while provisioning new instances.

renjith2cr gravatar imagerenjith2cr ( 2019-11-21 16:31:58 +0300 )edit

I can able to telnet to compute node from controller using port 6640 is working. But still getting same errorERROR neutron.agent.linux.async_process [-] Error received from [ovsdb-client monitor unix:C:\ProgramData\openvswitch\db.sock Bridge name --format=json]: 2019-11-22T05:53:25Z|00001|util|EMER

renjith2cr gravatar imagerenjith2cr ( 2019-11-22 07:54:02 +0300 )edit

ERROR nova.compute.manager nova.exception.PortBindingFailed: Binding failed for port 28e84322-d942-47ec-9401-74b40ff4ec13, please check neutron logs for more information.

renjith2cr gravatar imagerenjith2cr ( 2019-11-22 11:08:34 +0300 )edit

Hmm, recent Windows Sever versions include ovsdb binaries that may not work properly with neutron. One idea would be to update the PATH environment variable, making sure that the OVS binaries dir comes in front of paths such as C:\Windows\System32. This must be applied for the user running neutron.

lpetrut gravatar imagelpetrut ( 2019-11-24 16:46:22 +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

Stats

Asked: 2019-11-21 14:23:24 +0300

Seen: 10,300 times

Last updated: Dec 05 '19