Ask Your Question
0

Stein - failed to bind port [solved]

asked 2019-08-08 05:51:33 -0500

gsa gravatar image

updated 2019-08-08 10:57:15 -0500

Hello,

Problem: cannot launch instance due to 'Failed to bind port' issue

UPDATE 1: I tried to create an instance (with a user of the project (gsa) on the self service network:

$ openstack server create --flavor m1.nano --image cirros --nic net-id=b02469e7-c354-4884-a5be-aa5c2e1448fa --security-group default --key-name gsa-key provider-instance

Unfortunately, I got the same problem:

2019-08-08 14:50:42.828 20590 ERROR neutron.plugins.ml2.managers [req-1de99778-12ed-4d01-a600-4165a6d014b0 8daaad220fe944c598ab881dd66073e9 7eb45702a8aa42e8a26b1e22bc509edb - default default] Failed to bind port 5c5a8f91-2f6c-4298-a273-e20e104a0c85 on host compute for vnic_type normal using segments [{'id': '7e3e6124-f24d-448e-8f25-09d57db681f5', 'network_type': 'vxlan', 'physical_network': None, 'segmentation_id': 45, 'network_id': 'b02469e7-c354-4884-a5be-aa5c2e1448fa'}]

This is my first Openstack install. I followed the installation guide with the following configuration:

  • 1 host: Ubuntu Server 18.04.2 -- IP: 192.168.150.2
  • 3 VMs:
    • openstack-controller: Ubuntu Server 18.04.2 -- IP: 192.168.150.100
    • openstack-compute: Ubuntu Server 18.04.2 -- IP: 192.168.150.101
    • openstack-block-storage: Ubuntu Server 18.04.2 -- IP: 192.168.150.102

I didn't go for a management network interface and everything is configured to go through the only VM interface.

The VMs connect to the external world through a bridge interface:

host$ brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.068c8231ba09       yes             enp1s0
                                                        vnet0
                                                        vnet2
                                                        vnet4

From the installation guide, I followed the Neutron option 2 to install VXLAN. I didn't do any specific network configuration on the VMs (didn't install OpenSwitch or anything as it wasn't mentioned in the guide).

The only issue I got from the installation process is https://ask.openstack.org/en/question/123115/is-it-possible-to-deploy-stein-on-ubuntu-1804/ (this one) but I'm not sure it has any impact on my issue.

I know that some others reported the Failed to bind port... issue but either they were talking about OpenVSwitch or another issue that resulted in roughly the same error message, that's the reason why I believe my issue is different.

Here are some information from my config:

$ openstack compute service list
+----+----------------+------------+----------+---------+-------+----------------------------+
| ID | Binary         | Host       | Zone     | Status  | State | Updated At                 |
+----+----------------+------------+----------+---------+-------+----------------------------+
|  1 | nova-scheduler | controller | internal | enabled | up    | 2019-08-08T10:19:23.000000 |
|  6 | nova-conductor | controller | internal | enabled | up    | 2019-08-08T10:19:26.000000 |
|  7 | nova-compute   | compute    | nova     | enabled | up    | 2019-08-08T10:19:27.000000 |
+----+----------------+------------+----------+---------+-------+----------------------------+

$ openstack volume service list
+------------------+-------------+------+---------+-------+----------------------------+
| Binary           | Host        | Zone | Status  | State | Updated At                 |
+------------------+-------------+------+---------+-------+----------------------------+
| cinder-scheduler | controller  | nova | enabled | up    | 2019-08-08T09:56:58.000000 |
| cinder-volume    | storage@lvm | nova | enabled | up    | 2019-08-08T09:57:08.000000 |
+------------------+-------------+------+---------+-------+----------------------------+

$ openstack network agent list
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
| ID                                   | Agent Type         | Host       | Availability Zone | Alive | State | Binary                    |
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
| 2bf3b534-9caa-4d77-868d-4da8801cf018 | Metadata agent     | controller | None              | :-)   | UP    | neutron-metadata-agent    |
| b04141e5-6728-44cc-a851-549de0cac87f | Linux bridge agent | controller | None              | :-)   | UP    | neutron-linuxbridge-agent |
| bc27f3ae-1025-49fd-af48-b7ece635ea7b | L3 agent           | controller | nova              | :-)   | UP    | neutron-l3-agent          |
| bcbe4d03-b49d-497f-89d9-dd5c50179f3f | DHCP agent         | controller | nova              | :-)   | UP    | neutron-dhcp-agent        |
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+

$ openstack network list
+--------------------------------------+------------------+--------------------------------------+
| ID                                   | Name             | Subnets                              |
+--------------------------------------+------------------+--------------------------------------+
| 3346533d-3fe7-47f3-9819-ed6121a9cb18 | provider         | 0584f848-f69f-44f1-bc6c-e3fcd8d266c4 |
| b02469e7-c354-4884-a5be-aa5c2e1448fa | wiki-selfservice | 02e80244-f389-4870-b0f4-0a981a9d919d |
+--------------------------------------+------------------+--------------------------------------+

The configuration file of neutron was done following the installation guide:

[DEFAULT]
core_plugin = ml2
service_plugins = router
allow_overlapping_ips = true
auth_strategy = keystone
notify_nova_on_port_status_changes = true
notify_nova_on_port_data_changes = true
transport_url = rabbit://openstack:<PWD>@controller
[agent]
root_helper = "sudo /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf"
[cors]
[database]
connection = mysql+pymysql://neutron:<PWD>@controller/neutron
[keystone_authtoken]
www_authenticate_uri = http://controller ...
(more)
edit retag flag offensive close merge delete

Comments

Which user launches the instance?

If you followed the instruction, the provider network is not shared, so that a non-admin user doesn't have the right to attach instances to it. You can share it with openstack network set --share.

Bernd Bausch gravatar imageBernd Bausch ( 2019-08-08 06:07:43 -0500 )edit

Actually, in the installation guide, it is configured as a shared network. Here's the command that was run:

openstack network create --share --external --provider-physical-network provider --provider-network-type flat provide

Done with a user of the project (gsa) but with admin, it's the same

gsa gravatar imagegsa ( 2019-08-08 06:31:34 -0500 )edit

I stand corrected.

Can you launch an instance on the self service network?

Bernd Bausch gravatar imageBernd Bausch ( 2019-08-08 09:20:53 -0500 )edit

Still have the same issue :-( I have updated my post with the command and error logs (UPDATE 1).

gsa gravatar imagegsa ( 2019-08-08 09:54:12 -0500 )edit

Thanks to your help, I figured it out! I will post a reply to my question to document it.

gsa gravatar imagegsa ( 2019-08-08 10:35:41 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-08-08 10:43:18 -0500

gsa gravatar image

I figured it out!

The issue (as stupid as it sounds) is that I simply didn't configure the compute node. The logs kept on saying: 'Failed to bind port 5c5a8f91-2f6c-4298-a273-e20e104a0c85 on host compute...' and that triggered something in me.

After installing the missing parts on the compute node, I could see the compute network agent:

$  openstack network agent list
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
| ID                                   | Agent Type         | Host       | Availability Zone | Alive | State | Binary                    |
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
| 2bf3b534-9caa-4d77-868d-4da8801cf018 | Metadata agent     | controller | None              | :-)   | UP    | neutron-metadata-agent    |
| 997f5dec-a05f-43fc-ae69-8de3e537f8b5 | Linux bridge agent | compute    | None              | :-)   | UP    | neutron-linuxbridge-agent |
| b04141e5-6728-44cc-a851-549de0cac87f | Linux bridge agent | controller | None              | :-)   | UP    | neutron-linuxbridge-agent |
| bc27f3ae-1025-49fd-af48-b7ece635ea7b | L3 agent           | controller | nova              | :-)   | UP    | neutron-l3-agent          |
| bcbe4d03-b49d-497f-89d9-dd5c50179f3f | DHCP agent         | controller | nova              | :-)   | UP    | neutron-dhcp-agent        |
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+

And I could launch my first instance (I still have some IP address issues in the instance, but I'll try to figure it out on my own first ;-))

I take this opportunity to say how great the installation guide documentation is. It's a real pleasure to go through it and see how it actually works perfectly (when you read it completely ;-)).

Thanks again for helping me see my unfortunate mistake!

edit flag offensive delete link more

Your Answer

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

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-08-08 05:51:33 -0500

Seen: 31 times

Last updated: Aug 08