Can't set project_name in auth_token fixture

Bug #1533463 reported by Jamie Lennox
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
keystonemiddleware
Fix Released
Low
Jamie Lennox

Bug Description

Most other parameters in the auth_token middleware fixture can set both the _id and _name parameter, It looks like project_name was simply forgotten.

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

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

Changed in keystonemiddleware:
assignee: nobody → Jamie Lennox (jamielennox)
status: New → In Progress
Changed in keystonemiddleware:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to keystonemiddleware (master)

Reviewed: https://review.openstack.org/266664
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=45f37903fb8998db27c134f72857d02d402543a8
Submitter: Jenkins
Branch: master

commit 45f37903fb8998db27c134f72857d02d402543a8
Author: Jamie Lennox <email address hidden>
Date: Wed Jan 13 14:43:56 2016 +1100

    Add project_name to the auth_token fixture

    User and domain options allow you to set the _id and _name values
    however project_name is missing. Add project_name to the available
    parameters and enhance the tests to check more variables are set.

    Closes-Bug: #1533463
    Change-Id: Ia19aad0ff9e5c7667f702466e998c44a40f9a673

Changed in keystonemiddleware:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/keystonemiddleware 4.1.0

This issue was fixed in the openstack/keystonemiddleware 4.1.0 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.