yahoo-eng-team team mailing list archive

[Ankit Agrawal <ankit11.agrawal@xxxxxxxxxxx>]

Public bug reported:

If the vm fails to spawn on the nova compute node where it was suppose
to run, then it reschedules to run the vm on the another compute node.
After the vm is created successfully on the another node, you will
notice that VM is assigned 2 fixed ip addresses.

Expected output: only one fixed ip address should be assigned to a VM.

Actual output:
openstack@development-009:/opt/stack/nova/nova/compute$ nova list
+--------------------------------------+-------------------------------------------+--------+------------+-------------+------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------------------------------------------+--------+------------+-------------+------------------------------+
| 42016c47-40c3-4562-b2b5-d3c8199cc4e6 | nova-42016c47-40c3-4562-b2b5-d3c8199cc4e6 | ACTIVE | - | Running | private=10.0.0.81, 10.0.0.82 |
+--------------------------------------+-------------------------------------------+--------+------------+-------------+------------------------------+

To reproduce this issue, you will need to explicitly raise Exception
from compute/manafger.py->_spawn method.

** Affects: nova
     Importance: Undecided
     Assignee: Ankit Agrawal (ankit11-agrawal)
         Status: New


** Tags: ntt

** Changed in: nova
     Assignee: (unassigned) => Ankit Agrawal (ankit11-agrawal)

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

Title:
  fixed ip address assigned twice to the vm

Status in OpenStack Compute (Nova):
  New

Bug description:
  If the vm fails to spawn on the nova compute node where it was suppose
  to run, then it reschedules to run the vm on the another compute node.
  After the vm is created successfully on the another node, you will
  notice that VM is assigned 2 fixed ip addresses.

  Expected output: only one fixed ip address should be assigned to a VM.

  Actual output:
  openstack@development-009:/opt/stack/nova/nova/compute$ nova list
  +--------------------------------------+-------------------------------------------+--------+------------+-------------+------------------------------+
  | ID | Name | Status | Task State | Power State | Networks |
  +--------------------------------------+-------------------------------------------+--------+------------+-------------+------------------------------+
  | 42016c47-40c3-4562-b2b5-d3c8199cc4e6 | nova-42016c47-40c3-4562-b2b5-d3c8199cc4e6 | ACTIVE | - | Running | private=10.0.0.81, 10.0.0.82 |
  +--------------------------------------+-------------------------------------------+--------+------------+-------------+------------------------------+

  To reproduce this issue, you will need to explicitly raise Exception
  from compute/manafger.py->_spawn method.

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