mistral requires auth_uri to point to v3 explicitly, to work

Bug #1620630 reported by kamal saurabh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
High
zhubingbing

Bug Description

mistral fails with keystone v3, unless auth_uri explicitly references v3

in file:
kolla/ansible/roles/mistral/templates/mistral.conf.j2

currently v3 is not explicit
[keystone_authtoken]
auth_uri = {{ internal_protocol }}://{{ kolla_internal_fqdn }}:{{ keystone_public_port }}

what works for me:
[keystone_authtoken]
auth_uri = {{ internal_protocol }}://{{ kolla_internal_fqdn }}:{{ keystone_public_port }}/v3

also it looks like mistral project is not going to support this,

https://ask.openstack.org/en/question/53473/mistral-authorization-failed-the-resource-could-not-be-found-http-404/

Adding logs,

LOGS:

2016-08-24 15:12:29.606 1 WARNING mistral.actions.openstack.base [-] Traceback (most recent call last):
  File "/var/lib/kolla/venv/lib/python2.7/site-packages/mistral/actions/openstack/base.py", line 79, in run
    method = self._get_client_method(self._get_client())
  File "/var/lib/kolla/venv/lib/python2.7/site-packages/mistral/actions/openstack/actions.py", line 60, in _get_client
    keystone_endpoint = keystone_utils.get_keystone_endpoint_v2()
  File "/var/lib/kolla/venv/lib/python2.7/site-packages/mistral/utils/openstack/keystone.py", line 114, in
    return get_endpoint_for_project('keystone')
  File "/var/lib/kolla/venv/lib/python2.7/site-packages/mistral/utils/openstack/keystone.py", line 76, in get_endpoint_for_project
    response = client().tokens.get_token_data(token, include_catalog=True)
  File "/var/lib/kolla/venv/lib/python2.7/site-packages/mistral/utils/openstack/keystone.py", line 35, in client
    auth_url=auth_url
  File "/var/lib/kolla/venv/lib/python2.7/site-packages/keystoneclient/v3/client.py", line 231, in __init__
    self.authenticate()
  File "/var/lib/kolla/venv/lib/python2.7/site-packages/positional/__init__.py", line 101, in inner
    return wrapped(*args, **kwargs)
  File "/var/lib/kolla/venv/lib/python2.7/site-packages/keystoneclient/httpclient.py", line 578, in authenticate
    resp = self.get_raw_token_from_identity_service(**kwargs)
  File "/var/lib/kolla/venv/lib/python2.7/site-packages/keystoneclient/v3/client.py", line 317, in get_raw_token_from_identity_service
    _('Authorization failed: %s') % e)
AuthorizationFailure: Authorization failed: The resource could not be found. (HTTP 404)

Changed in kolla:
status: New → Triaged
milestone: none → newton-rc2
Revision history for this message
zhubingbing (zhubingbing) wrote :
Changed in kolla:
status: Triaged → Confirmed
importance: Undecided → Low
Steven Dake (sdake)
Changed in kolla:
importance: Low → High
Changed in kolla:
assignee: nobody → zhubingbing (zhubingbing)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/384147

Changed in kolla:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/384147
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=96bfb5967c7812fa103ccd660a7adafc02dada57
Submitter: Jenkins
Branch: master

commit 96bfb5967c7812fa103ccd660a7adafc02dada57
Author: zhubingbing <email address hidden>
Date: Sun Oct 9 02:50:03 2016 +0000

    fix mistral requires auth_uri to point to v3 explicitly

    mistral create keystone client by using auth_uri to v3 explicitly[0]

    [0] https://github.com/openstack/mistral/blob/7685cdb1b653ecbeda28ad45adcc3196cb52767e/mistral/utils/openstack/keystone.py#L174,#L184

    Change-Id: Iff38204414289a9aa36232b2c461bc5bdde46e56
    Closes-Bug: #1620630

Changed in kolla:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 3.0.0.0rc2

This issue was fixed in the openstack/kolla 3.0.0.0rc2 release candidate.

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.