yahoo-eng-team team mailing list archive

[Hauke Bruno <1488820@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This issue occurs on a fresh OpenStack Kilo installation (Ubuntu 14.04
LTS) with a single non-HA network node:

In general public access via floating IPs works, I can ping, ssh and so
on my instances.

But if I associate a new floating IP to a new instance, all floating IPs
(including the new associated one) stop working (no ping and ssh
possible). The strange thing: If I just wait 5 minutes or doing "service
openvswitch-switch restart" manually, everything went back working like
a charm.

I checked all neutron and ovs logs, but there aren't any errors.

Is there any periodic task running in the background every 5 minutes
which could affect that behavior?

cheers,
hauke

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

Title:
  All floating IPs stop working after associating a new one

Status in neutron:
  New

Bug description:
  This issue occurs on a fresh OpenStack Kilo installation (Ubuntu 14.04
  LTS) with a single non-HA network node:

  In general public access via floating IPs works, I can ping, ssh and
  so on my instances.

  But if I associate a new floating IP to a new instance, all floating
  IPs (including the new associated one) stop working (no ping and ssh
  possible). The strange thing: If I just wait 5 minutes or doing
  "service openvswitch-switch restart" manually, everything went back
  working like a charm.

  I checked all neutron and ovs logs, but there aren't any errors.

  Is there any periodic task running in the background every 5 minutes
  which could affect that behavior?

  cheers,
  hauke

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