unable to create volume in cinder

Bug #1389687 reported by Sinh Lam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Invalid
Undecided
Unassigned

Bug Description

When using LVM backend in new JUNO install, getting the following error when trying to create a test volume:

2014-11-05 13:01:59.835 2831 WARNING cinder.context [-] Arguments dropped when creating context: {'user': u'9077df4d2a1f4e568212cb9628bb1f29', 'tenant': u'01cb84bc296e4c9ba917d616100a899d', 'user_identity': u'9077df4d2a1f4e568212cb9628bb1f29 01cb84bc296e4c9ba917d616100a899d - - -'}
2014-11-05 13:01:59.839 2831 ERROR oslo.messaging.rpc.dispatcher [req-e98e33db-1371-4e5b-ac55-7e3aadecf949 9077df4d2a1f4e568212cb9628bb1f29 01cb84bc296e4c9ba917d616100a899d - - -] Exception during message handling: create_volume() got an unexpected keyword argument 'source_replicaid'
2014-11-05 13:01:59.839 2831 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last):
2014-11-05 13:01:59.839 2831 TRACE oslo.messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply
2014-11-05 13:01:59.839 2831 TRACE oslo.messaging.rpc.dispatcher incoming.message))
2014-11-05 13:01:59.839 2831 TRACE oslo.messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 176, in _dispatch
2014-11-05 13:01:59.839 2831 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args)
2014-11-05 13:01:59.839 2831 TRACE oslo.messaging.rpc.dispatcher File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 122, in _do_dispatch
2014-11-05 13:01:59.839 2831 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args)
2014-11-05 13:01:59.839 2831 TRACE oslo.messaging.rpc.dispatcher TypeError: create_volume() got an unexpected keyword argument 'source_replicaid'
2014-11-05 13:01:59.839 2831 TRACE oslo.messaging.rpc.dispatcher
2014-11-05 13:01:59.841 2831 ERROR oslo.messaging._drivers.common [req-e98e33db-1371-4e5b-ac55-7e3aadecf949 9077df4d2a1f4e568212cb9628bb1f29 01cb84bc296e4c9ba917d616100a899d - - -] Returning exception create_volume() got an unexpected keyword argument 'source_replicaid' to caller
2014-11-05 13:01:59.841 2831 ERROR oslo.messaging._drivers.common [req-e98e33db-1371-4e5b-ac55-7e3aadecf949 9077df4d2a1f4e568212cb9628bb1f29 01cb84bc296e4c9ba917d616100a899d - - -] ['Traceback (most recent call last):\n', ' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply\n incoming.message))\n', ' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 176, in _dispatch\n return self._do_dispatch(endpoint, method, ctxt, args)\n', ' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 122, in _do_dispatch\n result = getattr(endpoint, method)(ctxt, **new_args)\n', "TypeError: create_volume() got an unexpected keyword argument 'source_replicaid'\n"]

the command being passed is:

cinder create --display-name sinh_test7 1

this leaves the volume in a perpetual state of 'creating' status. cannot remove/delete. resetting the state does nothing as well.

ii cinder-common 1:2014.1.3-0ubuntu1 all Cinder storage service - common files
ii cinder-volume 1:2014.1.3-0ubuntu1 all Cinder storage service - Volume server
ii python-cinder 1:2014.1.3-0ubuntu1 all Cinder Python libraries

included is the cinder.conf (minus ip and password info).

Revision history for this message
Sinh Lam (slam-c) wrote :
Revision history for this message
Sinh Lam (slam-c) wrote :

this is because of a version difference between what's on the controller and what's on the storage nodes.

updated the storage nodes to the same as the controller (2014.2-0ubuntu1~cloud0) and the error disappeared.

Changed in cinder:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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