Cinder Issues

Sean McGinnis sean.mcginnis at gmx.com
Mon Oct 12 21:47:23 UTC 2020


> did it ever work? Check the cinder logs, the service is apparently not
> running. Double check your cinder configuration and keystone endpoint
> for cinder.
Based on these logs, it actually appears to be an issue with the
keystone deployment, not Cinder. So not to say there isn't something
going on with Cinder too, but from this output it is never even getting
there since it doesn't get past the first step of authenticating.
>> RESP: [503] Connection: keep-alive Content-Length: 218 Content-Type:
>> application/json Date: Mon, 12 Oct 2020 13:50:26 GMT
>> X-Openstack-Request-Id: req-1db26997-7450-4586-a106-70fc9804ee82
>> RESP BODY: {"message": "The server is currently unavailable. Please
>> try again at a later time.<br /><br />\nThe Keystone service is
>> temporarily unavailable.\n\n", "code": "503 Service Unavailable",
>> "title": "Service Unavailable"}
>> GET call to volumev2 for
>> http://10.10.1.53:8776/v2/7929351d491347788f5de228e135e67c/os-services
>> used request id req-1db26997-7450-4586-a106-70fc9804ee82
>> The server is currently unavailable. Please try again at a later
>> time.<br /><br />
>> The Keystone service is temporarily unavailable.
>>
>> (HTTP 503)



More information about the openstack-discuss mailing list