Create Volume from Image Failing on non-LVM Configuration

Bug #1163468 reported by Joe T
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Unassigned
Folsom
Won't Fix
Medium
Unassigned

Bug Description

Hello,

I'm currently using Folsom. I haven't tested if this still exists in Grizzly.

I was able to successfully create a volume from a Glance image by using the standard LVM Cinder configuration. However, it fails immediately in my other environment which uses the NetApp iSCSI driver:

2013-04-02 11:11:26 26208 ERROR cinder.openstack.common.rpc.amqp [-] Exception during message handling
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp Traceback (most recent call last):
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp File "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py", line 276, in _process_data
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp rval = self.proxy.dispatch(ctxt, version, method, **args)
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp File "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/dispatcher.py", line 145, in dispatch
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp return getattr(proxyobj, method)(ctxt, **kwargs)
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 174, in create_volume
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp self._copy_image_to_volume(context, volume_ref, image_id)
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 335, in _copy_image_to_volume
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp self.db.volume_update(context, volume_id, {'status': 'error'})
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp self.gen.next()
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 327, in _copy_image_to_volume
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp image_id)
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp File "/usr/lib/python2.7/dist-packages/cinder/volume/driver.py", line 628, in copy_image_to_volume
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp with utils.temporary_chown(volume_path):
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp return self.gen.next()
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp File "/usr/lib/python2.7/dist-packages/cinder/utils.py", line 1012, in temporary_chown
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp orig_uid = os.stat(path).st_uid
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp OSError: [Errno 2] No such file or directory: '/dev/mapper/cinder--volumes-volume--2c8e5316--5a94--4c7a--9ef7--0663c49feecf'
2013-04-02 11:11:26 26208 TRACE cinder.openstack.common.rpc.amqp

I'm not sure why it's trying to reach the volume under /dev/mapper -- it sounds like Cinder is falling back to a default function?

Please let me know if you need further information.

Thanks,
Joe

Revision history for this message
John Griffith (john-griffith) wrote :

Hey Joe,

In Folsom this currently only works on LVM and Ceph. Hoping to have a backport for the general iSCSI case soon.

Changed in cinder:
status: New → Triaged
importance: Undecided → Medium
status: Triaged → Fix Released
importance: Medium → Undecided
Revision history for this message
Joe T (joe-topjian-v) wrote :

Hi John,

Thanks for the quick reply. If there are plans for a backport, then is it safe to assume this is fixed in Grizzly?

Thanks,
Joe

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.