setup_keystone_certs does not support use with keystone v3 API

[James Hebden]

The ceph-radosgw charm is hard-coded in the 17.02 release to use the v2 Keystone API. This fails when the environment is configured for v3 Keystone, for example when multiple domains are in use.

[James Hebden (ec0)]

See here for change used in place to work around this issue:
https://git.launchpad.net/~jhebden/charm-ceph-radosgw/diff/hooks/utils.py?h=onsite-fixes-17.02&id=0d89d4dd60a819ec2444abad82151cd8db3431d3

[James Page (james-page)]

This is fixed in the development version of the charm, which is yet unreleased.

[James Page (james-page)]

I stand corrected - that fix is in the 17.02 release.

[James Page (james-page)]

This impacts on deployments using SSL with keystone v3 only.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/469679
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-radosgw/commit/?id=41943502b305c02779050649a7659849a61b68b0
Submitter: Jenkins
Branch: master

commit 41943502b305c02779050649a7659849a61b68b0
Author: David Ames <email address hidden>
Date: Wed May 31 15:48:42 2017 -0700

    Handle SSL and Keystone v3

    When using SSL and Keystone v3 the charm was hardcoding v2.0 in the
    URL.

    This change adapts based on what is passed from keystone.

    Change-Id: Ib08730e6480b1b1706c450075ac2f7312e3e5f59
    Closes-Bug: #1691875