yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

I'm closing this bug as invalid as I can't find appropriate bug to duplicate this to.
AFAIK, this issue was on the nova side where VM could not successfully operate after reboot.
RIght now it is fixed.

** Changed in: neutron
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1325737

Title:
  Public network connectivity check failed after VM reboot

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  This is query to identify this kind of failures:
  http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiYWZ0ZXIgMTggYXR0ZW1wdHNcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQwMTc0MDkxMTYxNX0=

  Public connectivity issue appears after instance reboot.

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