| 2014-01-24 11:34:58 |
Chinmaya Bharadwaj |
bug |
|
|
added bug |
| 2014-01-24 11:34:58 |
Chinmaya Bharadwaj |
attachment added |
|
compute.log https://bugs.launchpad.net/bugs/1272286/+attachment/3955812/+files/compute.log |
|
| 2014-01-24 11:41:40 |
Chinmaya Bharadwaj |
summary |
VMware driver: Nova compute fails to start when two proxies are present per vcenter |
VMware driver: Nova compute fails to start when multiple nova compute services are running per vCenter. |
|
| 2014-01-24 11:42:31 |
Chinmaya Bharadwaj |
description |
Nova Compute fails to start when there are more than one proxy per vCenter (two nova compute services running on different vms) and instances are provisioned in the clusters.
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.
log file attached. |
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, for the load balancing
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.
log file attached. |
|
| 2014-01-24 11:48:46 |
Chinmaya Bharadwaj |
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, for the load balancing
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.
log file attached. |
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) 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.
log file attached. |
|
| 2014-01-24 11:49:47 |
Chinmaya Bharadwaj |
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) 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.
log file attached. |
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) 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. |
|
| 2014-01-24 11:52:03 |
Chinmaya Bharadwaj |
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) 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. |
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. |
|
| 2014-01-26 15:07:03 |
Gary Kotton |
nova: status |
New |
Confirmed |
|
| 2014-01-26 17:01:28 |
Gary Kotton |
nova: importance |
Undecided |
High |
|
| 2014-01-26 17:01:32 |
Gary Kotton |
nova: milestone |
|
icehouse-3 |
|
| 2014-01-26 17:01:34 |
Gary Kotton |
nova: assignee |
|
Gary Kotton (garyk) |
|
| 2014-01-31 06:13:10 |
Gary Kotton |
nova: importance |
High |
Critical |
|
| 2014-02-09 14:56:32 |
Gary Kotton |
nova: status |
Confirmed |
In Progress |
|
| 2014-02-11 22:41:34 |
Joe Gordon |
nova: importance |
Critical |
High |
|
| 2014-02-17 15:14:46 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2014-02-24 23:59:34 |
Tracy Jones |
bug task added |
|
openstack-vmwareapi-team |
|
| 2014-02-25 21:34:45 |
Tracy Jones |
openstack-vmwareapi-team: status |
New |
Fix Committed |
|
| 2014-02-25 21:34:48 |
Tracy Jones |
openstack-vmwareapi-team: importance |
Undecided |
High |
|
| 2014-02-25 22:56:19 |
Tracy Jones |
tags |
nova vmware |
havana-backport-potential nova vmware |
|
| 2014-03-05 13:08:42 |
Thierry Carrez |
nova: status |
Fix Committed |
Fix Released |
|
| 2014-03-18 23:35:00 |
Sabari Murugesan |
nova: status |
Fix Released |
In Progress |
|
| 2014-03-18 23:35:00 |
Sabari Murugesan |
nova: milestone |
icehouse-3 |
icehouse-rc1 |
|
| 2014-03-18 23:35:00 |
Sabari Murugesan |
nova: assignee |
Gary Kotton (garyk) |
Sabari Murugesan (smurugesan) |
|
| 2014-03-18 23:35:35 |
Sabari Murugesan |
openstack-vmwareapi-team: status |
Fix Committed |
In Progress |
|
| 2014-03-18 23:35:35 |
Sabari Murugesan |
openstack-vmwareapi-team: assignee |
|
Sabari Murugesan (smurugesan) |
|
| 2014-03-24 13:23:59 |
Russell Bryant |
tags |
havana-backport-potential nova vmware |
havana-backport-potential icehouse-rc-potential nova vmware |
|
| 2014-03-24 13:24:06 |
Russell Bryant |
nova: milestone |
icehouse-rc1 |
|
|
| 2014-03-25 00:25:52 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2014-03-25 09:03:53 |
Russell Bryant |
nova: milestone |
|
icehouse-rc1 |
|
| 2014-03-31 19:04:08 |
Thierry Carrez |
nova: status |
Fix Committed |
Fix Released |
|
| 2014-04-09 23:49:26 |
OpenStack Infra |
tags |
havana-backport-potential icehouse-rc-potential nova vmware |
havana-backport-potential icehouse-rc-potential in-stable-havana nova vmware |
|
| 2014-04-17 09:13:39 |
Thierry Carrez |
nova: milestone |
icehouse-rc1 |
2014.1 |
|
| 2014-09-22 13:09:40 |
Alan Pevec |
nominated for series |
|
nova/havana |
|
| 2014-09-22 13:09:41 |
Alan Pevec |
bug task added |
|
nova/havana |
|
| 2014-09-22 17:39:58 |
Alan Pevec |
nova/havana: status |
New |
Fix Committed |
|
| 2014-09-22 17:39:58 |
Alan Pevec |
nova/havana: milestone |
|
2013.2.4 |
|
| 2014-09-22 22:24:04 |
Alan Pevec |
nova/havana: status |
Fix Committed |
Fix Released |
|
