ovs-agent fails when configuring 2 datanetworks to the same interface

Bug #1980376 reported by Pedro Monteiro Azevedo de Moura Almeida
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Invalid
Low
Unassigned

Bug Description

Brief Description
-----------------
OVS-Agent fails to setup when there's more than 1 datanetwork for the same interface.
If the deployment manager configuration file is set up like this:

- class: data
      dataNetworks:
      - group0-data0
      - group0-data0b
      name: data0
      platformNetworks: []
      port:
        name: eth1000
      ptpRole: none

then you will get the following error:

2022-05-24 17:19:10.855 1130 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Parsing bridge_mappings failed: Value br-phy0 in mapping: 'group0-data0b:br-phy0' not unique. agent terminated!

Also, if you try to create to another bridge mapping to the same interface, you will get:
[root@controller-0 ~]# ovs-vsctl add-br br-phy2
[root@controller-0 ~]# ovs-vsctl list-br
br-int
br-phy0
br-phy1
br-phy2
br-tun
[root@controller-0 ~]# ovs-vsctl add-port br-phy2 eth1000
ovs-vsctl: cannot create a port named eth1000 because a port named eth1000 already exists on bridge br-phy0

Severity
--------
Major

Steps to Reproduce
------------------
1. Install Stx-6.0 w/ the dm-config.yaml set with more than 1 datanetwork on the same interface like [1]
2. Apply stx-openstack
3. The application may or may not apply, but either way, the neutron-ovs-agent pod should die eventually

[1] - class: data
      dataNetworks:
      - group0-data0
      - group0-data0b
      name: data0
      platformNetworks: []
      port:
        name: eth1000
      ptpRole: none

Expected Behavior
------------------
ovs agent running correctly:
openstack neutron-ovs-agent-compute-0-5621f953-hs4zz 1/1 Running 0 4h40m
Actual Behavior
----------------
ovs agent fails to run:
openstack neutron-ovs-agent-compute-0-5621f953-hs4zz 0/1 CrashLoopBackOff 57 4h40m

Reproducibility
---------------
100%

System Configuration
--------------------
AIO Simplex

Branch/Pull Time/Commit
-----------------------
OS="centos"
SW_VERSION="22.02"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID="20220420T033744Z"

Last Pass
---------
Unclear

Timestamp/Logs
--------------
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl logs neutron-ovs-agent-controller-1-cab72f56-znbmt -n openstack
+ exec neutron-openvswitch-agent --config-file /etc/neutron/neutron.conf --config-file /tmp/pod-shared/neutron-agent.ini --config-file /tmp/pod-shared/ml2-local-ip.ini --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --config-file /etc/neutron/plugins/ml2/ml2_conf.ini
2022-05-24 17:19:03.924 1130 INFO neutron.common.config [-] Logging enabled!
2022-05-24 17:19:03.925 1130 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-openvswitch-agent version 16.4.3.dev56
2022-05-24 17:19:04.972 1130 INFO neutron.agent.agent_extensions_manager [-] Loaded agent extensions: []
2022-05-24 17:19:07.928 1130 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [-] Bridge br-int has datapath-ID 000062bb22749042
2022-05-24 17:19:10.855 1130 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Parsing bridge_mappings failed: Value br-phy0 in mapping: 'group0-data0b:br-phy0' not unique. agent terminated!

Test Activity
-------------
Developer Testing

Ghada Khalil (gkhalil)
tags: added: stx.distro.openstack stx.networking
Changed in starlingx:
importance: Undecided → Low
Changed in starlingx:
status: New → Incomplete
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.