Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1862890

Summary: [OSP16.1] Deletion of ML2OVS agents fails during migration to OVN
Product: Red Hat OpenStack Reporter: Roman Safronov <rsafrono>
Component: python-networking-ovnAssignee: Jakub Libosvar <jlibosva>
Status: CLOSED DUPLICATE QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: apevec, jlibosva, jpretori, lhh, majopela, oblaut, scohen
Target Milestone: z2Keywords: Triaged
Target Release: ---   
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: 2020-08-07 14:33:40 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:

Description Roman Safronov 2020-08-03 06:54:07 UTC
Description of problem:


After performing ML2OVS to ML2OVN migration procedure according to the documentation procedure https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/networking_with_open_virtual_network/index#migrating-ml2ovs-to-ovn
ML2OVS agents still present.
Existing VMs are not accessible via network.

(overcloud) [stack@undercloud-0 ~]$ openstack network agent list
+--------------------------------------+------------------------------+---------------------------+-------------------+-------+-------+-------------------------------+
| ID                                   | Agent Type                   | Host                      | Availability Zone | Alive | State | Binary                        |
+--------------------------------------+------------------------------+---------------------------+-------------------+-------+-------+-------------------------------+
| 1a9041f0-6d0f-4cc8-bc6a-a29e9e5e3048 | DHCP agent                   | controller-1.redhat.local | nova              | XXX   | UP    | neutron-dhcp-agent            |
| 270038fc-d919-4f45-90dc-8cffef0a6aeb | Open vSwitch agent           | compute-1.redhat.local    | None              | XXX   | UP    | neutron-openvswitch-agent     |
| 3b8edbd2-4ab0-48a8-9101-488c99d77164 | Metadata agent               | controller-2.redhat.local | None              | XXX   | UP    | neutron-metadata-agent        |
| 56127db5-373d-4389-80b3-bd45173f1376 | Open vSwitch agent           | controller-1.redhat.local | None              | XXX   | UP    | neutron-openvswitch-agent     |
| 59089c9b-bca5-4817-987e-242116198b4c | DHCP agent                   | controller-0.redhat.local | nova              | XXX   | UP    | neutron-dhcp-agent            |
| 683f166f-be40-466c-871e-f16b14e5239c | DHCP agent                   | controller-2.redhat.local | nova              | XXX   | UP    | neutron-dhcp-agent            |
| 6deb2705-1cc5-4236-8872-4103d38ef043 | Open vSwitch agent           | controller-0.redhat.local | None              | XXX   | UP    | neutron-openvswitch-agent     |
| 7e539892-43f1-40a6-a127-66f2701ad72e | L3 agent                     | controller-0.redhat.local | nova              | XXX   | UP    | neutron-l3-agent              |
| 9c80d220-8cb2-4320-80b7-817d001cf0ff | Metadata agent               | controller-0.redhat.local | None              | XXX   | UP    | neutron-metadata-agent        |
| b6268a95-20bb-4304-b816-cdc8af96dba4 | Open vSwitch agent           | controller-2.redhat.local | None              | XXX   | UP    | neutron-openvswitch-agent     |
| b7f5d148-08ab-4ef8-9f40-1e8643e11bcb | L3 agent                     | controller-2.redhat.local | nova              | XXX   | UP    | neutron-l3-agent              |
| c0bade83-e0aa-4c2a-81e2-00e35f815632 | Open vSwitch agent           | compute-0.redhat.local    | None              | XXX   | UP    | neutron-openvswitch-agent     |
| de0d35d9-9057-4d26-9832-7a73b88a1ad1 | Metadata agent               | controller-1.redhat.local | None              | XXX   | UP    | neutron-metadata-agent        |
| ee4b13ac-9505-4f35-ad9c-2521973e2ddb | L3 agent                     | controller-1.redhat.local | nova              | XXX   | UP    | neutron-l3-agent              |
| a1ac09da-e8af-40d4-9ae2-0bce96788d8b | OVN Controller agent         | compute-0.redhat.local    | n/a               | :-)   | UP    | ovn-controller                |
| 1a1bf616-cbe0-4815-9769-9b56ff555e59 | OVN Metadata agent           | compute-0.redhat.local    | n/a               | :-)   | UP    | networking-ovn-metadata-agent |
| 57ec835c-3e2f-462d-8731-5067fe9f1395 | OVN Controller agent         | compute-1.redhat.local    | n/a               | XXX   | UP    | ovn-controller                |
| d840e3f4-28df-4053-8bc7-c24602b45bec | OVN Metadata agent           | compute-1.redhat.local    | n/a               | :-)   | UP    | networking-ovn-metadata-agent |
| d99ceb4a-3dac-410f-a75d-4935a5b7d771 | OVN Controller Gateway agent | controller-1.redhat.local | n/a               | XXX   | UP    | ovn-controller                |
| f6d7edf3-1835-4d8d-a294-17c65b2ad08e | OVN Controller Gateway agent | controller-2.redhat.local | n/a               | XXX   | UP    | ovn-controller                |
| 802e0f4a-d4a1-4414-b3f6-359d225497b6 | OVN Controller Gateway agent | controller-0.redhat.local | n/a               | XXX   | UP    | ovn-controller                |
+--------------------------------------+------------------------------+---------------------------+-------------------+-------+-------+-------------------------------+



Version-Release number of selected component (if applicable):
RHOS-16.1-RHEL-8-20200729.n.0
python3-networking-ovn-7.2.1-0.20200611133437.15f2281.el8ost.noarch
python3-networking-ovn-migration-tool-7.2.1-0.20200611133437.15f2281.el8ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Run ML2OVS to ML2OVN migration procedure according to the official documentation procedure https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/networking_with_open_virtual_network/index#migrating-ml2ovs-to-ovn
2.
3.

Actual results:
ML2OVS agents still exist after migration to OVN

Expected results:
ML2OVN agent does not exist. Only ML2OVN agents are available.

Additional info:

Comment 1 Jesse Pretorius 2020-08-05 10:10:54 UTC
I suspect that this expected result is (notice that the first item changes):

ML2OVS agent does not exist. Only ML2OVN agents are available.

Is there a possible workaround here?

Comment 2 Jakub Libosvar 2020-08-05 10:49:50 UTC
(In reply to Jesse Pretorius from comment #1)
> I suspect that this expected result is (notice that the first item changes):
> 
> ML2OVS agent does not exist. Only ML2OVN agents are available.
> 
> Is there a possible workaround here?

The workaround could be to go to the Neutron database and remove the agents manually.

However keep in mind the impact is just that the agents appear dead on agent list output but the agents won't be used and will not cause any networking problems. It can impact only services monitoring agents' liveness like Zabbix.

Comment 4 Jakub Libosvar 2020-08-07 14:33:40 UTC

*** This bug has been marked as a duplicate of bug 1828889 ***