yahoo-eng-team team mailing list archive

[smarta94 <1459724@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Scenario: Host A and Host B are dedicated compute nodes, separate from the controller which contains the neutron networking component.
1. Spawn an instance on Host A.
2. Associate a floating ip to it and verify that it can be reached via floating ip and namespace.
3. live-migrate the instance to the Host B.
4. After migration completes, verify that the instance can be reached (ping/ssh floating ip and via namespace).

Expected Behavior:
Networking of instance should be working fine (ping/ssh should work).

Actual Behavior:
Instance cannot be reached, however, the instance can reach out to everywhere it cannot be reached from (using the console is the only access to the instance, so somehow its still reached)

Furthermore, if the instance gets live-migrated back to the original
host, it can again be reached normally.

Branch: Juno 2014.2.1-1, python-novaclient 2.20.0-1

Which logs are needed for this?

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1459724

Title:
  live-migration causes lack of access to instance

Status in OpenStack Compute (Nova):
  New

Bug description:
  Scenario: Host A and Host B are dedicated compute nodes, separate from the controller which contains the neutron networking component.
  1. Spawn an instance on Host A.
  2. Associate a floating ip to it and verify that it can be reached via floating ip and namespace.
  3. live-migrate the instance to the Host B.
  4. After migration completes, verify that the instance can be reached (ping/ssh floating ip and via namespace).

  Expected Behavior:
  Networking of instance should be working fine (ping/ssh should work).

  Actual Behavior:
  Instance cannot be reached, however, the instance can reach out to everywhere it cannot be reached from (using the console is the only access to the instance, so somehow its still reached)

  Furthermore, if the instance gets live-migrated back to the original
  host, it can again be reached normally.

  Branch: Juno 2014.2.1-1, python-novaclient 2.20.0-1

  Which logs are needed for this?

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