yahoo-eng-team team mailing list archive

[Aaron Rosen <aaronorosen@xxxxxxxxx>]

Public bug reported:

If a nova-compute machine restarts when openvswitch comes up it logs the
following warning messages for all tap interfaces that do not exist:

bridge|WARN|could not open network device tap2cf7dbad-9d (No such
device)

Once the compute-node  starts it recreates the interfaces and re-adds them to the
ovs-bridge. Unfortunately, ovs does not reinitialize the interfaces as they
are already in ovsdb and does not assign them a ofport number.

This situation corrects itself though the next time a port is added to the
ovs-bridge which is why no one has probably noticed this issue till now.

In order to correct this we should first remove interface that exist and
then readd them.

same bug on neutron-side:
https://bugs.launchpad.net/neutron/+bug/1268762

** Affects: nova
     Importance: Medium
     Assignee: Aaron Rosen (arosen)
         Status: In Progress


** Tags: havana-backport-potential network

** Changed in: nova
     Assignee: (unassigned) => Aaron Rosen (arosen)

** Tags added: network

** Changed in: nova
   Importance: Undecided => Medium

** Tags added: havana-backport-potential

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1270973

Title:
  Remove and recreate interface if already exists

Status in OpenStack Compute (Nova):
  In Progress

Bug description:
  If a nova-compute machine restarts when openvswitch comes up it logs
  the following warning messages for all tap interfaces that do not
  exist:

  bridge|WARN|could not open network device tap2cf7dbad-9d (No such
  device)

  Once the compute-node  starts it recreates the interfaces and re-adds them to the
  ovs-bridge. Unfortunately, ovs does not reinitialize the interfaces as they
  are already in ovsdb and does not assign them a ofport number.

  This situation corrects itself though the next time a port is added to the
  ovs-bridge which is why no one has probably noticed this issue till now.

  In order to correct this we should first remove interface that exist and
  then readd them.

  same bug on neutron-side:
  https://bugs.launchpad.net/neutron/+bug/1268762

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