ovs-agent fails to start because only sriov datanetwork is configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Triaged
|
Low
|
Unassigned |
Bug Description
Brief Description
-----------------
The ovs-agent will fail to start if only sriov datanetwork is configured. Because the bridge_mappings which is 'bridge_mappings: public:br-ex' won't be changed if no normal datanetwork configured. The ovs-agent fails to start because it can't find bridge br-ex which doesn't exit on the host.
Severity
--------
Minor
Steps to Reproduce
------------------
1. Only configure a sriov datanetwork during set up StarlingX and do not configure any other datanetwork:
system datanetwork-add physnet0 vlan
system host-if-modify -m 1500 -n sriov -c pci-sriov -N 5 controller-0 ${DATA0IFUUID}
system interface-
2. After stx-openstack applied, check the status of ovs agent:
system application-list
kubectl get pod -n openstack | grep ovs-agent
Expected Behavior
------------------
ovs agent running correctly:
neutron-
Actual Behavior
----------------
ovs agent fails to run:
neutron-
Reproducibility
---------------
100%
System Configuration
-------
AIO Simplex
Branch/Pull Time/Commit
-------
BUILD_DATE=
Last Pass
---------
Unclear
Timestamp/Logs
--------------
kubectl logs -n openstack neutron-
+ exec neutron-
2019-07-12 11:18:46.772 590 INFO neutron.
2019-07-12 11:18:46.772 590 INFO neutron.
2019-07-12 11:18:46.772 590 INFO neutron.
2019-07-12 11:18:46.772 590 INFO neutron.
2019-07-12 11:18:47.560 590 INFO neutron.
2019-07-12 11:18:47.560 590 INFO neutron.
2019-07-12 11:18:48.514 590 INFO neutron.
2019-07-12 11:18:48.514 590 INFO neutron.
2019-07-12 11:18:51.641 590 INFO neutron.
2019-07-12 11:18:51.641 590 INFO neutron.
2019-07-12 11:18:51.641 590 ERROR neutron.
2019-07-12 11:18:51.641 590 ERROR neutron.
system helm-override-show stx-openstack neutron openstack
```
| | neutron_ovs-agent: |
| | hosts: |
| | - conf: |
| | auto_bridge_add: {} |
| | plugins: |
| | openvswitch_agent: |
| | agent: {} |
| | ovs: |
| | datapath_type: system |
| | integration_bridge: br-int |
| | vhostuser_
| | sriov_agent: |
| | agent: |
| | root_helper: "" |
| | securitygroup: |
| | firewall_driver: noop |
| | sriov_nic: |
| | physical_
| | name: controller-0 |
| | neutron_
| | hosts: |
| | - conf: |
| | auto_bridge_add: {} |
| | plugins: |
| | openvswitch_agent: |
| | agent: {} |
| | ovs: |
| | datapath_type: system |
| | integration_bridge: br-int |
| | vhostuser_
| | sriov_agent: |
| | agent: |
| | root_helper: "" |
| | securitygroup: |
| | firewall_driver: noop |
| | sriov_nic: |
| | physical_
| | name: controller-0
```
Test Activity
-------------
Developer Testing
bridge_mappings is set as public:br-ex initially: /github. com/openstack/ stx-config/ blob/master/ kubernetes/ applications/ stx-openstack/ stx-openstack- helm/stx- openstack- helm/manifests/ manifest. yaml#L1201
https:/
If no normal datanetwork is configured, the bridge_mappings won't be changed and ovs agent will fail to start.