Public network connectivity check failed after VM reboot

[Eugene Nikanorov]

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

Public connectivity issue appears after instance reboot.

[Andres Buraschi (andres-buraschi)]

Eugene, I'm not able to reproduce it using fedora default image (devstack). The test is:
1) Create new instance, allocate new floating IP and assign to instance.
2) Check that the VM is accessible through ping and ssh.
3) Soft reboot / Hard reboot the VM.
4) Check that the VM is NOT accessible through ping or ssh anymore.

After rebooting I'm able to access the instance. I also tried rebooting from cmd (sudo reboot).
Is this a issue happening only in tempest? (the trace shown in the given link explicits tempest test)

I'm glad to help if some more information can be given.
Regards.

[Eugene Nikanorov (enikanorov)]

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.

[Takahiro Shida (shida)]

It looks already fix on nova rights?
Please point it here.