Bug 2012717
| Summary: | [OSP16.2] DPDK instance is not reachable after ovs to ovn migration | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Maxim Babushkin <mbabushk> |
| Component: | python-networking-ovn | Assignee: | Jaganathan Palanisamy <jpalanis> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Eran Kuris <ekuris> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 16.2 (Train) | CC: | apevec, hakhande, jlibosva, jpalanis, lhh, majopela, oblaut, scohen, supadhya |
| Target Milestone: | z3 | Keywords: | Triaged |
| Target Release: | 16.2 (Train on RHEL 8.4) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-06-13 13:27:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1925290 | ||
The first NFV support for NFV will be in 17.1 and the issue is not happening in 17.1 closing the bz. |
Description of problem: DPDK instances are not reachable after ovs -> ovn migration Version-Release number of selected component (if applicable): OSP 16.2 RHOS-16.2-RHEL-8-20210923.n.1 How reproducible: Deploy the OVS based DPDK setup. Perform the OVS to OVN migration. Check availability of the dpdk instance. Actual results: The dpdk instance is not accessible anymore after the migration. Expected results: The dpdk instance should remain accessible. Additional info: The only error message I found in the logs was in a neutron log: 2021-10-10 14:23:53.787 26406 DEBUG neutron.agent.common.async_process [-] Output received from [ovsdb-client monitor tcp:127.0.0.1:6640 Interface name,ofport,external_ids --format=js on]: None _read_stdout /usr/lib/python3.6/site-packages/neutron/agent/common/async_process.py:262 2021-10-10 14:23:53.787 26406 DEBUG neutron.agent.common.async_process [-] Halting async process [ovsdb-client monitor tcp:127.0.0.1:6640 Interface name,ofport,external_ids --format=json] in response to an error. stdout: [[]] - stderr: [['2021-10-10T14:23:53Z|00001|fatal_signal|WARN|terminating with signal 15 (Terminated)']] _handle_process_error /usr/lib/python3.6/site-packages/neutron/agent/common/async_process.py:219 2021-10-10 14:23:53.787 26406 DEBUG neutron.agent.linux.utils [-] Running command: ['kill', '-9', '27051'] create_process /usr/lib/python3.6/site-packages/neutron/agent/linux/utils.py:88 2021-10-10 14:23:53.800 26406 ERROR neutron.agent.common.async_process [-] Error received from [ovsdb-client monitor tcp:127.0.0.1:6640 Interface name,ofport,external_ids --format=json]: None 2021-10-10 14:23:53.802 26406 DEBUG oslo_privsep.comm [-] EOF on privsep read channel _reader_main /usr/lib/python3.6/site-packages/oslo_privsep/comm.py:162 In additional, in the computes, there was a non existing bridge that appeared after the migration: Bridge "br-link0,dpdk-data0" Port "br-link0,dpdk-data0" Interface "br-link0,dpdk-data0" type: internal error: "could not add network device br-link0,dpdk-data0 to ofproto (Invalid argument)" The name of the bridge combined from the bridge mapping string and contains one part of bridge name and other part of physnet. The bridge of "br-link0" actually exists and functioning.