[Openstack] Cinder issues...
Remo Mattei
remo at italy1.com
Tue Apr 8 23:50:34 UTC 2014
you need to check your logs!!
> Whoops, I got too eager and tried to change the value to 'error'. Now I can't seem to do anything with nova or cinder...
>
> # nova list
> ERROR: <attribute 'message' of 'exceptions.BaseException' objects> (HTTP 500)
>
> # cinder list
> ERROR: <attribute 'message' of 'exceptions.BaseException' objects> (HTTP 500)
>
> I switched the value back to 'attaching' but I'm stuck with no command line cinder or nova (I get the error above for all commands).... I seem to kind of be able to do things with horizon however, but not everything.. Did I mess it up bad?
>
> I rebooted my controller and cinder nodes (and all associated api's and services)and it still won't work... I have a feeling I screwed something up by changing that value in mysql... Any pointers much appreciated... :(
>
>
> On 04/08/14 16:28, Remo Mattei wrote:
>> I just found it
>>
>> force-delete
>>
>>
>>
>>
>>> Arg, I think I see the issue... I created my cinder endpoints to
>>> point to thew wrong internal hosts. I fixed the endpoints, but the
>>> volume still sits in "Attaching" state, so I can't touch it.
>>>
>>> Should I manually tweak mysql to fix this? I see:
>>>
>>> mysql> use cinder;
>>>
>>> mysql> select * from volumes\G
>>> *************************** 1. row ***************************
>>> created_at: 2014-04-08 21:36:17
>>> updated_at: 2014-04-08 21:36:17
>>> deleted_at: 2014-04-08 21:37:52
>>> deleted: 1
>>> id: 756ca5f0-bcdf-40e9-a62c-26a648be753f
>>> ec2_id: NULL
>>> user_id: f8fdf7f84ad34c439c4075b5e3720211
>>> project_id: f7e61747885045d8b266a161310c0094
>>> host: NULL
>>> size: 10
>>> availability_zone: nova
>>> instance_uuid: NULL
>>> mountpoint: NULL
>>> attach_time: NULL
>>> status: deleted
>>> attach_status: detached
>>> scheduled_at: NULL
>>> launched_at: NULL
>>> terminated_at: NULL
>>> display_name: test-volume-1
>>> display_description: Just testing yo.
>>> provider_location: NULL
>>> provider_auth: NULL
>>> snapshot_id: NULL
>>> volume_type_id: NULL
>>> source_volid: NULL
>>> bootable: 0
>>> attached_host: NULL
>>> provider_geometry: NULL
>>> _name_id: NULL
>>> encryption_key_id: NULL
>>> migration_status: NULL
>>> *************************** 2. row ***************************
>>> created_at: 2014-04-08 21:38:52
>>> updated_at: 2014-04-08 21:42:44
>>> deleted_at: NULL
>>> deleted: 0
>>> id: e34524ea-cd2f-41e8-b37e-ac15456275d7
>>> ec2_id: NULL
>>> user_id: f8fdf7f84ad34c439c4075b5e3720211
>>> project_id: f7e61747885045d8b266a161310c0094
>>> host: genome-cloudstore
>>> size: 10
>>> availability_zone: nova
>>> instance_uuid: NULL
>>> mountpoint: NULL
>>> attach_time: NULL
>>> status: attaching
>>> attach_status: detached
>>> scheduled_at: 2014-04-08 21:38:52
>>> launched_at: 2014-04-08 21:38:53
>>> terminated_at: NULL
>>> display_name: test-volume-1
>>> display_description: Just testing.
>>> provider_location: NULL
>>> provider_auth: NULL
>>> snapshot_id: NULL
>>> volume_type_id: NULL
>>> source_volid: NULL
>>> bootable: 0
>>> attached_host: NULL
>>> provider_geometry: NULL
>>> _name_id: NULL
>>> encryption_key_id: NULL
>>> migration_status: NULL
>>> 2 rows in set (0.00 sec)
>>>
>>> I can change the value of 'status' from 'attaching' to 'error'... In
>>> theory I can delete it then. Any reason why I shouldn't do that?
>>>
>>> Thanks,
>>> -erich
>>>
>>>
>>> On 04/08/14 15:27, Erich Weiler wrote:
>>>
>>> _______________________________________________
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to : openstack at lists.openstack.org
>>> <mailto:openstack at lists.openstack.org>
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>
>>
>
> !DSPAM:1,53448b07261691310584250!
>
More information about the Openstack
mailing list