** Project changed: nova => cinder -- 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/1248630
Title: Cinder fails attaching volume after upgrade to Grizzly Status in Cinder: New Bug description: When attaching an existing volume (only existing volumes) the cinder- volume daemon fails with the next message: 2013-11-06 16:47:46 ERROR [cinder.openstack.common.rpc.common] ['Traceback (most recent call last):\n', ' File "/usr/lib/python2.7 /dist-packages/cinder/openstack/common/rpc/amqp.py", line 430, in _process_data\n rval = self.proxy.dispatch(ctxt, version, method, **args)\n', ' File "/usr/lib/python2.7/dist- packages/cinder/openstack/common/rpc/dispatcher.py", line 133, in dispatch\n return getattr(proxyobj, method)(ctxt, **kwargs)\n', ' File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 574, in attach_volume\n return do_attach()\n', ' File "/usr/lib/python2.7/dist- packages/cinder/openstack/common/lockutils.py", line 228, in inner\n retval = f(*args, **kwargs)\n', ' File "/usr/lib/python2.7/dist- packages/cinder/volume/manager.py", line 546, in do_attach\n raise exception.InvalidVolume(reason=msg)\n', 'InvalidVolume: Invalid volume: being attached by another instance\n'] The reason is that the instance_uuid in the volumes table in cinder database was set to 0, and it needs to be set to NULL, otherwise the cinder/volume/manager.py program fails. I think the database upgrade script should include the change from 0 to null, I'm doing it myself. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1248630/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
