Gnocchi triggering keystone error

asked 2017-12-13 18:26:47 -0500

anonymous user



On my attempts to run the script trying to install the Gnocchi plugin integrated with Ceilometer, I'm getting the following output as the result:

+./                      create_keystone_accounts
ne:create_keystone_accounts:383  local admin_project
++lib/keystone:create_keystone_accounts:384  openstack project show admin -f value -c id
Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL.
Could not determine a suitable URL for the plugin
+lib/keystone:create_keystone_accounts:384  admin_project=
+lib/keystone:create_keystone_accounts:1   exit_trap
+./                  local r=1
++./                  jobs -p
+./                  jobs=
+./                  [[ -n '' ]]
+./                  kill_spinner
+./               '[' '!' -z '' ']'
+./                  [[ 1 -ne 0 ]]
+./                  echo 'Error on exit'
Error on exit
+./                  generate-subunit 1513110720 4151 fail
+./                  [[ -z /opt/stack/logs ]]
+./                  /opt/stack/devstack/tools/ -d /opt/stack/logs
World dumping... see /opt/stack/logs/worlddump-2017-12-12-214111.txt for details
+./                  exit 1

This is the content of my local.conf file:



enable_plugin heat stable/ocata
enable_plugin tacker stable/ocata
enable_plugin ceilometer stable/ocata
enable_plugin aodh stable/ocata

The error only shows up when the line "CEILOMETER_BACKEND=gnocchi" is added to the local.conf file. The installation is successful otherwise.

After some research, I've seen cases where similar problems were solved by adding the machine's ip to the no_proxy variable or by commenting a few lines of the script, but none of these solutions worked for me. Does anyone know what can be done to solve this problem?

edit retag flag offensive close merge delete


The error Discovering versions from the identity service failed probably means that Keystone crashed. In any case, it's not accessible. Do you see anything in the Keystone log, or perhaps Apache log? Or another error further up in the log?

Bernd Bausch gravatar imageBernd Bausch ( 2017-12-14 04:54:59 -0500 )edit

Hello Bernd,

I hope I'm not messing up the logs that you are talking about.

On the access log of apache, I see that "GET /identity/v3/ HTTP/1.1" requests returned the error code 500. On the error log, the only abnormal thing I see is "AH00491: caught SIGTERM, shutting down".

acassimiro gravatar imageacassimiro ( 2017-12-14 05:37:08 -0500 )edit

On the keystone log there are only debug messages.

I'm not really sure what this means. I've used the same local.conf file to successfully deploy a devstack instance on another machine a week ago, and thats why I'm really confused right now.

acassimiro gravatar imageacassimiro ( 2017-12-14 05:39:10 -0500 )edit

Error 500 means that Apache can't talk to Keystone. The SIGTERM is probably irrelevant and comes from shutting everything down when fails.

You now have the task to find out where the 500 comes from. First check if Keystone is running at all.

Bernd Bausch gravatar imageBernd Bausch ( 2017-12-14 08:24:16 -0500 )edit

I've just tested the script again and after receiving the error message, I've checked the status of apache and keystone. Apache is active and running, while the keystone service is inactive. Since I'm pretty new to Devstack and its plugins, I'll keep trying to look for any relevant log information.

acassimiro gravatar imageacassimiro ( 2017-12-14 13:21:31 -0500 )edit