murano uses deprecated keystone auth config

Bug #1766642 reported by Vladislav Belogrudov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Invalid
Undecided
Unassigned

Bug Description

when running murano api with current configuration template:

2017-12-11 07:41:27.360 1 WARNING keystonemiddleware.auth_token [-] AuthToken
middleware is set with keystone_authtoken.service_token_roles_required set to
False. This is backwards compatible but deprecated behaviour. Please set this
to True.
2017-12-11 07:41:27.361 1 WARNING keystonemiddleware.auth_token [-] Use of
the auth_admin_prefix, auth_host, auth_port, auth_protocol, identity_uri,
admin_token, admin_user, admin_password, and admin_tenant_name configuration
options was deprecated in the Mitaka release in favor of an auth_plugin and
its related options. This class may be removed in a future release.
2017-12-11 07:41:27.362 1 WARNING keystonemiddleware.auth_token [-]
Configuring admin URI using auth fragments was deprecated in the Kilo
release, and will be removed in the Newton release, use 'identity_uri\
instead.

To fix these warnings and errors in future it is necessary to use service_token_roles_required = True

Revision history for this message
p.cipriano (ctpeter) wrote :

What about this?

[Thu May 10 22:12:48.490651 2018] [:error] [pid 93] UserWarning: Using keystoneclient sessions has been deprecated. Please update your software to use keystoneauth1.Recoverable error: {"explanation": "The server has either erred or is incapable of performing the requested operation.", "code": 500, "error": {"message": "(http://107.105.135.163:5000/v2.0/tokens): The resource could not be found. (HTTP 404) (Request-ID: req-940ead56-69d5-4695-b466-98682b6dea3e)", "traceback": null, "type": "NotFound"}, "title": "Internal Server Error"} (HTTP 500)
[Thu May 10 22:16:38.277824 2018] [:error] [pid 90] Recoverable error: {"explanation": "The server has either erred or is incapable of performing the requested operation.", "code": 500, "error": {"message": "(http://107.105.135.163:5000/v2.0/tokens): The resource could not be found. (HTTP 404) (Request-ID: req-7648253e-99b8-4a86-9aee-95cf96d40a31)", "traceback": null, "type": "NotFound"}, "title": "Internal Server Error"} (HTTP 500)

Revision history for this message
Michal Nasiadka (mnasiadka) wrote :

Not a bug in kolla-ansible

Changed in kolla-ansible:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.