Public bug reported:
Description
===
In a multi hypervisor environment containing esx computes and KVM computes, and
cinder VMDK backend configured,
When attaching a volume to a KVM INSTANCE, A volume is created in the vCenter
if a volume of type VMDK.
The volume VM is created in the cl
** Changed in: nova
Status: Invalid => 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/1602740
Title:
VMware: Sparse disks get attached to the instance as lazy
** Changed in: nova
Status: New => Invalid
--
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/1602740
Title:
VMware: Sparse disks get attached to the instance as lazy
Public bug reported:
Description
===
As per the documentation "Sparse disks get imported from the OpenStack Image
service into ESX as thin provisioned disks"
http://docs.openstack.org/kilo/config-reference/content/vmware.html
But its being set as lazy zeroedthick disk.
Steps to reprodu
agedObjectNotFound]
2014-11-19 06:05:55.086 29958 ERROR oslo_messaging.rpc.dispatcher Details:
{'obj': 'vm-1031'}
2014-11-19 06:05:55.086 29958 ERROR oslo_messaging.rpc.dispatcher
Environment
===
nova driver: VMWareVCDriver
cinder driver: VMDkdriver
Observing the issue
The issue exists in python-openstackclient, not in nova. Moving it to
openstackclient
** Project changed: nova => python-openstackclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launch
ance:
0a55fe16-3a21-40f0-85f3-777d6254f215] VMwareDriverException: Invalid datastore
path '[localdatastore]
volume-c279ad39-f1f9-4861-9d00-2de8f6df7756/volume-c279ad39-f1f9-4861-9d00-2de8f6df7756.vmdk'.
** Affects: nova
Importance: Undecided
Assignee: Chinmaya Bharadwaj (acbharad
Public bug reported:
With the latest code, cluster as the compute driver, Taking a snapshot
is failing with following error :
ERROR oslo_messaging.rpc.dispatcher [req-9c49bfdd-641c-4022-90cc-aae697e387f3
admin admin] Exception during message handling: Error occurred while opening
URL: https:/
** Changed in: horizon
Status: New => Invalid
** Changed in: nova
Status: Invalid => In Progress
** Changed in: horizon
Assignee: Chinmaya Bharadwaj (acbharadwaj) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
nce'\n"]
2014-04-04 03:05:41.629 WARNING nova.scheduler.driver
[req-cc690e5a-2bf3-4566-a697-30ca882df815 nova service] [instance:
f0abb23a-943a-475d-ac63-69d2563362cb] Setting instance to ERROR state.
** Affects: nova
Importance: Undecided
Assignee: Chinmaya Bharadwaj (acbhara
*** This bug is a duplicate of bug 1302482 ***
https://bugs.launchpad.net/bugs/1302482
Public bug reported:
when there is a Datacenter with no host , i.e an empty cluster, nova boot
fails.
The scheduler log error trace
Error from last host: devstack (node domain-c162(Demo-1)): [u'Traceback
Public bug reported:
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 s
12 matches
Mail list logo
