yahoo-eng-team team mailing list archive

[Yang Li <yang.li@xxxxxxxxxxxx>]

The bug was resolved in the last version, but not a indirect way, it was fixed because of self.plugin_rpc.register_legacy_notification_callbacks, in this function it will notify the local agent to update the port again, so the port will be handle twice, the second update will refresh firewall rule, and write the port to sg_port_map.
The get_or_create_ofport still remove the port from sg_port_map, and not added it back, perhaps it will be a hidden bug for some other situations.

** Changed in: neutron
       Status: Invalid => 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/1825295

Title:
  The openflow won't be deleted when we reboot and migrate the instance

Status in neutron:
  New

Bug description:
  Sometimes user will do some steps for instance management:
  1. Restart hostA neutron-openvswitch-agent
  2. Reboot the instance which in hostA
  3. Migrate the instance from hostA to hostB or resize the instance(this also cause migration)

  Then we will find the instance's openflows on the hostA still exist,
  this will cause instance connectivity problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1825295/+subscriptions