yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #11791
[Bug 1272286] Re: VMware driver: Nova compute fails to start when multiple nova compute services are running per vCenter.
The completely fix this bug we also need
https://review.openstack.org/#/c/69262/. This patch makes sure that the
driver lists only the instances of it's nodes. Currently, it lists all
the vm's that are with the hypervisor even the ones not managed by its
nodes.
** Changed in: nova
Status: Fix Released => In Progress
** Changed in: nova
Milestone: icehouse-3 => icehouse-rc1
** Changed in: nova
Assignee: Gary Kotton (garyk) => Sabari Murugesan (smurugesan)
** Changed in: openstack-vmwareapi-team
Status: Fix Committed => In Progress
** Changed in: openstack-vmwareapi-team
Assignee: (unassigned) => Sabari Murugesan (smurugesan)
--
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/1272286
Title:
VMware driver: Nova compute fails to start when multiple nova compute
services are running per vCenter.
Status in OpenStack Compute (Nova):
In Progress
Status in The OpenStack VMwareAPI subTeam:
In Progress
Bug description:
Nova Compute fails to start when there are multiple nova compute
services running on different VMs(nova compute VMs) and each Vm
managing multiple cluster in a vCenter and instances are provisioned
on them.
Explanation:
Lets say, one nova compute vm(C1) is managing 5 clusters, and
another(C2) managing 5 clusters. C1 manages n number of instances.
Suppose in C2 compute service gets restarted, it fails to start.
Reason:
on the start up of the nova-compute, it checks the instances reported by the driver are still associated with this host. If they are not, it destroys them.
method _destroy_evacuated_instances calls the driver list_instances, which lists all the instances in the vCenter, though they are managed by different compute. Instead it should return only the vms which are managed by c1/c2.
log file attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1272286/+subscriptions
References