Horizon does not properly support using Keystone v3 endpoints

Bug #1478996 reported by Jesse Pretorius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Medium
Jesse Pretorius
Kilo
Fix Released
Medium
Jesse Pretorius
Trunk
Fix Released
Medium
Jesse Pretorius

Bug Description

If the Keystone API endpoints are all v3, the login through Horizon will fail.

The OPENSTACK_API_VERSIONS section in local_settings needs to include '"identity": 3' when the Keystone endpoint used by Horizon is a v3 endpoint.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

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

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

Reviewed: https://review.openstack.org/206575
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=fb6438e8d85d27ca1af0f4dfefe8fbaf05fdff01
Submitter: Jenkins
Branch: master

commit fb6438e8d85d27ca1af0f4dfefe8fbaf05fdff01
Author: Jesse Pretorius <email address hidden>
Date: Tue Jul 28 15:57:41 2015 +0100

    Enable Horizon to consume a Keystone v3 API endpoint

    This patch enables Horizon to consume a Keystone v3 API endpoint.

    This patch also introduces two variables to allow the endpoint to be
    specified independently if required:
     - horizon_keystone_host: this defaults to the internal LB IP address
     - horizon_keystone_endpoint: this defaults to the internal Keystone
       endpoint

    This patch also does the following:
     - properly consumes the horizon_ssl_no_verify role setting;
     - includes a little comment cleanup which does nothing but clutter
       the local_settings configuration file.

    Closes-Bug: #1478996
    Change-Id: I5b7ceeecab072ead6fd380dcef7a48f1978a56f2

Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/208012

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

Reviewed: https://review.openstack.org/208012
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=da0269ec0737509dc1405859c3b53d731f339462
Submitter: Jenkins
Branch: kilo

commit da0269ec0737509dc1405859c3b53d731f339462
Author: Jesse Pretorius <email address hidden>
Date: Tue Jul 28 15:57:41 2015 +0100

    Enable Horizon to consume a Keystone v3 API endpoint

    This patch enables Horizon to consume a Keystone v3 API endpoint.

    This patch also introduces two variables to allow the endpoint to be
    specified independently if required:
     - horizon_keystone_host: this defaults to the internal LB IP address
     - horizon_keystone_endpoint: this defaults to the internal Keystone
       endpoint

    This patch also does the following:
     - properly consumes the horizon_ssl_no_verify role setting;
     - includes a little comment cleanup which does nothing but clutter
       the local_settings configuration file.

    Closes-Bug: #1478996
    Change-Id: I5b7ceeecab072ead6fd380dcef7a48f1978a56f2
    (cherry picked from commit fb6438e8d85d27ca1af0f4dfefe8fbaf05fdff01)

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

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.