| Thread Previous • Date Previous • Date Next • Thread Next |
Public bug reported:
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
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1686405
Title:
Wrong port status after some operations
Status in neutron:
New
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1686405/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
