Public network connectivity check failed after VM reboot

Bug #1325737 reported by Eugene Nikanorov
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Tags: gate-failure
Revision history for this message
Andres Buraschi (andres-buraschi) wrote :

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.

Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

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
Revision history for this message
Takahiro Shida (shida) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers