VMware: Volume creation fails when config 'vmware_volume_folder' contains special characters
Bug #1356794 reported by
Vipin Balachandran
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Vipin Balachandran |
Bug Description
Set vmware_
> cinder create 1
fails with following error:
Unable to find suitable datastore for volume of size: 1 GB under host: (obj){
value = "host-361"
_type = "HostSystem"
}. More details: Server raised fault: 'The name '/cinder-volumes' already exists
Changed in cinder: | |
milestone: | none → juno-rc1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
vCenter server escapes special characters in the folder name using URL encoding and returns back the encoded string while querying. This causes the check for folder existence to fail.
The workaround is to use folder name without '/', '\' or '% ' for vmware_ volume_ folder option value.