Yeah I just traced that down as well,
I verified that /usr/share/midonet-api/WEB-INF/web.xml has the correct keystone information:
The admin token below matches the one in /etc/keystone/keystone.conf
I even tried restarting the tomcat service and re-running the midonet-restart-neutron.pp manifest with the same errors in the logs.
<!-- Keystone configuration -->
<context-param>
<param-name>keystone-service_protocol</param-name>
<param-value>http</param-value>
</context-param>
<context-param>
<param-name>keystone-service_host</param-name>
<param-value>10.7.214.2</param-value>
</context-param>
<context-param>
<param-name>keystone-service_port</param-name>
<param-value>35357</param-value>
</context-param>
<context-param>
<param-name>keystone-admin_token</param-name>
<param-value>PnlhOhgK</param-value>
</context-param>
<!-- This tenant name is used to get the scoped token from Keystone, and
should be the tenant name of the user that owns the token sent in the
request -->
<context-param>
<param-name>keystone-tenant_name</param-name>
<param-value>admin</param-value>
</context-param>
Yeah I just traced that down as well, midonet- api/WEB- INF/web. xml has the correct keystone information: keystone. conf restart- neutron. pp manifest with the same errors in the logs.
I verified that /usr/share/
The admin token below matches the one in /etc/keystone/
I even tried restarting the tomcat service and re-running the midonet-
<!-- Keystone configuration --> name>keystone- service_ protocol< /param- name> value>http< /param- value> name>keystone- service_ host</param- name> value>10. 7.214.2< /param- value> name>keystone- service_ port</param- name> value>35357< /param- value> name>keystone- admin_token< /param- name> value>PnlhOhgK< /param- value> name>keystone- tenant_ name</param- name> value>admin< /param- value>
<context-param>
<param-
<param-
</context-param>
<context-param>
<param-
<param-
</context-param>
<context-param>
<param-
<param-
</context-param>
<context-param>
<param-
<param-
</context-param>
<!-- This tenant name is used to get the scoped token from Keystone, and
should be the tenant name of the user that owns the token sent in the
request -->
<context-param>
<param-
<param-
</context-param>