Hi, I haven't used these functions, but I see on http://developer.openstack.org/api-ref-compute-v2-ext.html the device parameter should be provided as
"Name of the device such as, /dev/vdb. Omit or set this parameter to null for auto-assignment, if supported. If you specify this parameter, the device must not exist in the guest operating system." Seems that the 'auto' is reserved by the system, so attach_volume function of compute.drivers.openstack.py should omit this parameter if it is not specified (or if it is specified as 'auto'). Regards, Markos On Thu, Oct 1, 2015 at 8:29 AM, <[email protected]> wrote: > Hi, > > While attaching a volume to an instance in Openstack, if I omit the device > name or if I specify the device name as auto, attach_volume call errors out. > > Traceback (most recent call last): > File "attach_volume_v1.py", line 44, in <module> > success = driver.attach_volume(instances[0], volumes[0], device = > 'auto') > File > "/usr/lib/python2.7/site-packages/libcloud/compute/drivers/openstack.py", > line 226, in attach_volume > 'device': device, > File "/usr/lib/python2.7/site-packages/libcloud/common/openstack.py", > line 202, in request > raw=raw) > File "/usr/lib/python2.7/site-packages/libcloud/common/base.py", line > 799, in request > response = responseCls(**kwargs) > File > "/usr/lib/python2.7/site-packages/libcloud/compute/drivers/openstack.py", > line 1001, in __init__ > super(OpenStack_1_1_Response, self).__init__(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/libcloud/common/base.py", line > 143, in __init__ > headers=self.headers) > libcloud.common.exceptions.BaseHTTPError: 400 The supplied device path > (auto) is invalid. > > > -- > Greetings, > Anu Bhaskar > > ________________________________ > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise confidential information. If you have > received it in error, please notify the sender immediately and delete the > original. Any other use of the e-mail by you is prohibited. Where allowed > by local law, electronic communications with Accenture and its affiliates, > including e-mail and instant messaging (including content), may be scanned > by our systems for the purposes of information security and assessment of > internal compliance with Accenture policy. > > ______________________________________________________________________________________ > > www.accenture.com >
