Issue originally reported to the Octavia project: https://bugs.launchpad.net/octavia/+bug/2033392
During the failover of a loadbalancer, Octavia disables a port and waits for its status to be DOWN, but it never happens, the port is still ACTIVE (it impacts the duration of the failover in Octavia, but also the availability of the loadbalancer).
When a bound port is disabled, its status is expected to be switched to DOWN.
But with ML2/OVN, the port remains ACTIVE.
$ openstack server create --image cirros-0.5.2-x86_64-disk --flavor m1.nano --network public server1
[..]
| id | 7e392799-7a25-4ec6-a0ff-e479b3c37cc6 |
[..]
$ openstack port list --device-id 7e392799-7a25-4ec6-a0ff-e479b3c37cc6
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------+--------+
| ID | Name | MAC Address | Fixed IP Addresses | Status |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------+--------+
| 208c473c-4161-4c3a-ab9e-8444d7bc375f | | fa:16:3e:85:bc:ac | ip_address='172.24.4.251', subnet_id='9441b590-d9d4-4f8f-b4aa-838736070222' | ACTIVE |
| | | | ip_address='2001:db8::322', subnet_id='813adce0-21de-44c9-958a-6967441b8623' | |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------+--------+
$ openstack port show -c admin_state_up -c status 208c473c-4161-4c3a-ab9e-8444d7bc375f
+----------------+--------+
| Field | Value |
+----------------+--------+
| admin_state_up | UP |
| status | ACTIVE |
+----------------+--------+
# Disabling the port
$ openstack port set --disable 208c473c-4161-4c3a-ab9e-8444d7bc375f
$ openstack port show -c admin_state_up -c status 208c473c-4161-4c3a-ab9e-8444d7bc375f
+----------------+--------+
| Field | Value |
+----------------+--------+
| admin_state_up | DOWN |
| status | ACTIVE |
+----------------+--------+
Folks on #openstack-neutron confirmed that with ML2/OVS, the status is DOWN when the port is disabled.
I read a little the code and checked the logs, and to tell the truth lost in the details :-)
If I understand well (of course I can't represent >10 years of API evolution and the ideas behind it) the status field of the port could represent that the backend wiring was successful.
If the admin sets admin_state_
If we assume that OVS drivers behaviour is correct we have to make OVN driver behave the same way.
I would go and ask the drivers about it to be sure, but that's just my 2 cents.