VMDK driver picks invalid datastore
Bug #1220217 reported by
Kartik Bommepally
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Kartik Bommepally |
Bug Description
VMwareVcVmdkDriver picks invalid datastore for e.g. inaccessible or readOnly for volume creation (create/clone) and the operation eventually fails.
The driver must ignore such datastores that are readOnly or which are not accessible or mounted to the ESX server.
Work around is to manually un-mount/re-mount the datastore on ESX that which are not accessible and to remove read-only datastores.
Fix is to have a filter for such datastores.
Changed in cinder: | |
assignee: | nobody → Kartik Bommepally (kartikaditya) |
Changed in cinder: | |
milestone: | none → havana-rc1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-rc1 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/44862
Review: https:/