yahoo-eng-team team mailing list archive

[Bolke de Bruin <bolke.de.bruin@xxxxxx>]

Public bug reported:

I am trying to move from havana to icehouse on ubuntu 14.0.4. The
migration is failing because the ml2 migration is expecting the
portbindingsport table to contain all the ports. However my record count
in ports is 460 and in portsportbinding just 192. Thus only 192 records
get added to ml2_port_bindings.

The consequence of this is that the network-node and the compute nodes
are adding "unbound" interfaces in the ml2_port_bindings table.
Additionally nova-compute is update its network info with wrong
information causing a subsequent restart of nova-compute to fail with an
error of "vif_type=unbound". Besides that the instances on the nodes do
not get network connectivity.

Let's say I am happy that I made a backup, because the DB gets into a
inconsistent state every time now.

** 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/1437762

Title:
  portbindingsport does not have all ports causing ml2 migration failure

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I am trying to move from havana to icehouse on ubuntu 14.0.4. The
  migration is failing because the ml2 migration is expecting the
  portbindingsport table to contain all the ports. However my record
  count in ports is 460 and in portsportbinding just 192. Thus only 192
  records get added to ml2_port_bindings.

  The consequence of this is that the network-node and the compute nodes
  are adding "unbound" interfaces in the ml2_port_bindings table.
  Additionally nova-compute is update its network info with wrong
  information causing a subsequent restart of nova-compute to fail with
  an error of "vif_type=unbound". Besides that the instances on the
  nodes do not get network connectivity.

  Let's say I am happy that I made a backup, because the DB gets into a
  inconsistent state every time now.

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