kuryr-libnetwork keystonev3 support

Bug #1622302 reported by Antoni Segura Puimedon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-libnetwork
Fix Released
Critical
Antoni Segura Puimedon

Bug Description

Kuryr already has a bug for keystonev3 and is in progress to being merged. Now we have to add it for integrations. This bug is for fixing it for our Libnetwork integration.

affects: kuryr → kuryr-libnetwork
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr-libnetwork (master)

Reviewed: https://review.openstack.org/367033
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=d1353b38ae44ea46f4a0ee5883eb2a4f4384d505
Submitter: Jenkins
Branch: master

commit d1353b38ae44ea46f4a0ee5883eb2a4f4384d505
Author: Antoni Segura Puimedon <email address hidden>
Date: Thu Sep 8 02:58:26 2016 +0200

    auth: Add keystonev3 support

    In order to integrate with Kolla and to support newer deployments that
    have only keystonev3 enabled, we leverage keystoneauth1.

    I want to thank Fawad for taking a stab at fixing this earlier.

    Depends-On: Ia56b22963f5a2130a722403a14ee1a233ac6cff9
    Closes-bug: #1622302
    Change-Id: Id57420ef94ea9bd71b6581c4cdc24697465a3445
    Signed-off-by: Antoni Segura Puimedon <email address hidden>
    Co-authored-by: Liping Mao <email address hidden>

Changed in kuryr-libnetwork:
status: In Progress → Fix Released
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.