Bug 1704490 - neutron.plugins.ml2.managers Failed to bind port for spine leaf network topology
Summary: neutron.plugins.ml2.managers Failed to bind port for spine leaf network topology
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 15.0 (Stein)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Rodolfo Alonso
QA Contact: Roee Agiman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-29 22:24 UTC by Yuri Obshansky
Modified: 2019-05-21 14:33 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-21 14:33:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
neutron log (7.70 MB, text/plain)
2019-05-10 22:08 UTC, Yuri Obshansky
no flags Details
nova log (7.84 MB, text/plain)
2019-05-10 22:09 UTC, Yuri Obshansky
no flags Details
sos report (3.27 KB, application/x-xz)
2019-05-10 22:09 UTC, Yuri Obshansky
no flags Details

Description Yuri Obshansky 2019-04-29 22:24:51 UTC
Description of problem:
Openstack deployed with Spine -Leaf netwrok topology 
using the next templates
https://gitlab.cee.redhat.com/yobshans/rhos-qe-edge-stuff/tree/master/osp15
Instances created on Overcloud are not pingable

Found errors in /var/log/containers/neutron/server.log
2019-04-29 21:59:37.296 25 ERROR neutron.plugins.ml2.managers [req-de7d48d3-a59e-4f84-a3ab-0f6a2b15d367 0987497e65dd434eb63256f7e2f78420 d120123a294c4e5fbfe597e1d93a75a3 - default default] Failed to bind port b8de870d-eed6-4277-b60e-b156a4b9d899 on host site-undercloud-0.localdomain for vnic_type baremetal using segments [{'id': 'c647af7f-b3bd-4760-8327-99c85c8eb878', 'network_type': 'flat', 'physical_network': 'ctlplane', 'segmentation_id': None, 'network_id': '5181539c-01e9-4e67-9c8a-44233c14ab30'}, {'id': 'ba9ee18a-c9d8-4363-9f80-6e547ed01439', 'network_type': 'flat', 'physical_network': 'leaf1', 'segmentation_id': None, 'network_id': '5181539c-01e9-4e67-9c8a-44233c14ab30'}, {'id': '8a12209a-54d9-4bf1-86ee-4dbb2a6cb436', 'network_type': 'flat', 'physical_network': 'leaf2', 'segmentation_id': None, 'network_id': '5181539c-01e9-4e67-9c8a-44233c14ab30'}]

Port is 
(undercloud) [stack@site-undercloud-0 ~]$ openstack port list |grep b8de870d-eed6-4277-b60e-b156a4b9d899
| b8de870d-eed6-4277-b60e-b156a4b9d899 | Controller0-port-0                  | 52:54:00:0b:b6:a8 | ip_address='192.168.24.31', subnet_id='54276d9f-a820-4820-9af1-89585536eade' | DOWN   |


Version-Release number of selected component (if applicable):
RHOS_TRUNK-15.0-RHEL-8-20190423.n.1
python3-neutron-lib-1.25.0-0.20190312185238.fc2a810.el8ost.noarch
puppet-neutron-14.4.1-0.20190420042323.400fd54.el8ost.noarch
python3-neutronclient-6.12.0-0.20190312100012.680b417.el8ost.noarch

How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Yuri Obshansky 2019-05-10 22:08:14 UTC
Created attachment 1566833 [details]
neutron log

Comment 3 Yuri Obshansky 2019-05-10 22:09:14 UTC
Created attachment 1566834 [details]
nova log

Comment 4 Yuri Obshansky 2019-05-10 22:09:38 UTC
Created attachment 1566835 [details]
sos report

Comment 5 Yuri Obshansky 2019-05-10 22:29:29 UTC
Looks like it happened before Overcloud network/instance creation.
Probably, right after undercloud installation.
I used custom undercloud.conf
https://gitlab.cee.redhat.com/yobshans/rhos-qe-edge-stuff/blob/master/osp15/undercloud/undercloud.conf
Attached neutron/nova log files are after Overcloud deployment without any operations on Overcloud.

Comment 9 Yuri Obshansky 2019-05-15 11:38:57 UTC
Hello Rodolfo, 

Please, use this guide 
https://docs.google.com/document/d/1JR9l7BqROZGVSZV6QGDzelu_mQXA07wllAfQ9w3vFEY/edit#heading=h.xt4vut2c3ynx

Yuri

Comment 10 Yuri Obshansky 2019-05-15 15:56:15 UTC
Additional information which I forget to publish:

network-environment.yaml

NeutronNetworkVLANRanges: 'leaf0:1:1000,leaf1:1:1000,leaf2:1:1000'

network-environment-overrides.yaml

parameter_defaults:
  ControlPlaneSubnet: leaf0
  VipSubnetMap:
    ctlplane: leaf0
  NeutronFlatNetworks: leaf0,leaf1,leaf2
  ControllerParameters:
    NeutronBridgeMappings: "leaf0:br-ex"
  ComputeLeaf1Parameters:
    NeutronBridgeMappings: “leaf1:br-ex”
  ComputeLeaf2Parameters:
    NeutronBridgeMappings: “leaf2:br-ex”


Note You need to log in before you can comment on or make changes to this bug.