Wrong port status after some operations

[Dong Jun]

The environment is, openstack master branch, all in one devstack, openvswitch agent, dhcp agent.
After some operations, a nova port turns to wrong status. This issue can be reproduced by following steps:
1. Remove ovs port from ovs bridge using ovs-vsctl del-port command, neutron port status changed to down, that's right;[1]
2. Update name of the port, the port turns to ACTIVE status, that's wrong.[2]

It seems a problem of DHCP provisioning block, when updating port name, a DHCP provisioning block was added, then DHCP agent complete this provisioning block and make the port ACTIVE.

[1] After step 1:
| admin_state_up | True | binding:host_id | c4 | binding:vif_type | ovs | binding:vnic_type | normal
| device_owner | compute:nova
| id | cad2e6a0-5bda-4e4d-9232-ba7c06acf28e
| status | DOWN
| updated_at | 2017-04-26T13:32:22Z

[2] After step 2:
| admin_state_up | True | binding:host_id | c4 | binding:vif_type | ovs | binding:vnic_type | normal | device_owner | compute:nova | id | cad2e6a0-5bda-4e4d-9232-ba7c06acf28e | name | bbc | status | ACTIVE | updated_at | 2017-04-26T13:34:39Z

[Miguel Lavalle (minsel)]

Thanks for filing this bug. Would you please explain how the sequence of steps that you describe above reflect what may happen in a real deployment? Is this something that you have found or experienced in a real deployment?

[Dong Jun (dongj)]

The purpose of step 1 is to let ovs agent notify the neutron-server port down, unbounding port from ovs bridge is one of the approaches.
I just happen to find this issue when I was dealing with an provisioning block issue of networking-ovn[1], comparing the provisioning block behaviors between networking-ovn and neutron.
This issue does not seem to have a functional impact, but display status and real status are inconsistent.
[1] https://bugs.launchpad.net/networking-ovn/+bug/1686013

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Hello:

The reproducer involves operations not supported in OpenStack. We don't support manual OVS operations like "ovs-vsctl del-port". Any port creation/deletion/update should be done via OpenStack API; os-vif (Neutron in some cases) will be in charge of any operation on the device, depending on the backend.

Regards.