Group/role identity v3 commands have no option for domain to operate on

Bug #1446546 reported by Kalle Happonen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-openstackclient
Fix Released
Medium
Juan Antonio Osorio Robles

Bug Description

Many group and role commands fail against keystone v3 API when you have multiple domains with domain specific backends. This affects at least non-default domains.

When trying to add a user to a role, it gives

openstack role add --user test --project service admin
ERROR: openstack The request you have made requires authentication. (Disable debug mode to suppress these details.) (HTTP 401)

The group add user behaves the same way
openstack group add user testgroup test
ERROR: openstack The request you have made requires authentication. (Disable debug mode to suppress these details.) (HTTP 401)

There is no way to specify which domain is operated on for these commands.

Dean Troyer (dtroyer)
Changed in python-openstackclient:
status: New → Confirmed
importance: Undecided → Medium
Changed in python-openstackclient:
assignee: nobody → Juan Antonio Osorio Robles (juan-osorio-robles)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-openstackclient (master)

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

Changed in python-openstackclient:
status: Confirmed → In Progress
Changed in python-openstackclient:
status: In Progress → Fix Committed
Dean Troyer (dtroyer)
Changed in python-openstackclient:
milestone: none → m12
Changed in python-openstackclient:
status: Fix Committed → 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.