Cinder broken in new overcloud rocky

asked 2019-05-03 00:05:38 -0500

ARatcliff gravatar image

After a tripleo deployment the cinder service is broken. The deployment was aparently successful, but VMs fail to start with prepping block device

$ openstack volume list
ERROR: publicURL endpoint for volumev2 service not found
$ docker ps -a | grep -i cinder
-- no output --
$ grep -i cinder /var/lib/mistral/overcloud/ansible.log
-- no output --

What am I missing?

edit retag flag offensive close merge delete

Comments

Could it be that TripleO doesn't deploy volume v2? Try openstack --os-volume-api-version 3 volume list, and/or set the environment variable OS_VOLUME_API_VERSION to 3.

Bernd Bausch gravatar imageBernd Bausch ( 2019-05-03 01:15:09 -0500 )edit

$ OS_VOLUME_API_VERSION=3
$ export OS_VOLUME_API_VERSION
$ echo $OS_VOLUME_API_VERSION
3
$ openstack volume list
ERROR: publicURL endpoint for volumev3 service not found
If TripleO doesn't deploy v2, AND fails to correctly set the env. var. why isn't that written anywhere?

ARatcliff gravatar imageARatcliff ( 2019-05-03 01:29:46 -0500 )edit

Your cloud has neither v2 nor v3. Something did not work when you deployed Cinder. Time to check the log files. Sorry I don't know where TripleO keeps logs, but you could start with the Cinder log.

Bernd Bausch gravatar imageBernd Bausch ( 2019-05-03 01:58:04 -0500 )edit

Bernd, see my original question: specifically, $ grep -i cinder /var/lib/mistral/overcloud/ansible.log -- no output --

ARatcliff gravatar imageARatcliff ( 2019-05-03 02:04:22 -0500 )edit

Unfortunately I don't know enough about Tripleo to tell you where to look, let alone what to look for. The only statement I can make is that Cinder's deployment did not succeed or was not even attempted. This is the point where you need to start investigating.

Bernd Bausch gravatar imageBernd Bausch ( 2019-05-03 04:33:30 -0500 )edit