Openstack volume service list: The server is currently unavailable. Please try again at a later time. (HTTP 503)

asked 2018-09-04 13:52:59 -0600

um3rella gravatar image

updated 2018-09-10 15:19:16 -0600

cinder-scheduler is active on controller and cinder-volume service is active on block1.

I have checked the cinder.conf configuration files on both nodes for correctness according to the guide multiple times.

I added an additional field under [keystone_auth] --> auth_uri = http://controller:5000 which was missing from the guide and seemed to resolve a sqlite3 pymysql error

I am no longer getting errors in cinder-scheduler.log file or cinder-volume.log on block1, but when I try to verify cinder volume services, I get a HTTP503 server error. All the other services and openstack CLI verification step work as described.

At this point, I don't know how I would go about debugging this problem. What log files other than cinder-scheduler would you look at? Any feedback or help is greatly appreciated, Thanks

I added an additional field, auth_uri, under keystone_auth in cinder.conf and the database errors seems to be resolved.

I am still getting a HTTP 503 error when using any of the cinder openstack commands.

edit retag flag offensive close merge delete

Comments

This looks like cinder-api is not running or not accessible. To confirm, run other Cinder commands like openstack volume list. Which guide and which step are you referring to?

If the API process is running, first confirm that Cinder’s catalog entry is correct.

Bernd Bausch gravatar imageBernd Bausch ( 2018-09-04 15:07:25 -0600 )edit

Non of the Cinder Openstack commands are working, but OpenStack CLI commands for other services work fine. I am referring the the Cinder (Queens guide), I have tried install on 16.04.04 and 16.04.05.

um3rella gravatar imageum3rella ( 2018-09-10 15:17:43 -0600 )edit

So either the Cinder services aren’t running or they are not connected to the web server correctly. Use systemctl status to find out if they are up. If not, check their logs for reasons why they are down.

Bernd Bausch gravatar imageBernd Bausch ( 2018-09-10 17:28:09 -0600 )edit