Bug 2227124 - If another admin user exist in another domain beside the default one, tripleo-ansible breaks
Summary: If another admin user exist in another domain beside the default one, tripleo...
Keywords:
Status: POST
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: tripleo-ansible
Version: 16.2 (Train)
Hardware: x86_64
OS: All
low
low
Target Milestone: z9
: 16.2 (Train on RHEL 8.4)
Assignee: Takashi Kajinami
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On: 2222058
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-28 04:18 UTC by Takashi Kajinami
Modified: 2023-08-16 13:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2222058
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 889914 0 None MERGED Add the admin role for admin in default domain 2023-08-16 13:41:39 UTC
Red Hat Issue Tracker OSP-26985 0 None None None 2023-07-28 04:19:38 UTC

Description Takashi Kajinami 2023-07-28 04:18:35 UTC
+++ This bug was initially created as a clone of Bug #2222058 +++

Description of problem:
If another admin user exist in another domain beside the default one, deployment consistently fails
in tripleo-keystone-resources role because of the "Multiple matches found for admin" error.

```
2023-07-11 12:34:56,789 p=123456 u=mistral n=ansible | TASK [tripleo-keystone-resources : Assign admin role to admin project for admin user] ***
2023-07-11 12:34:56,789 p=123456 u=mistral n=ansible | Tuesday 11 July 2023  12:34:56 +0000 (0:00:01.234)       XX:XX:XX.XXX ********** 
2023-07-11 12:34:56,789 p=123456 u=mistral n=ansible | fatal: [undercloud]: FAILED! => {"changed": false, "msg": "Multiple matches found for admin"}
```


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a non-default domain
2. Create an "admin" user in that domain
3. Run deployment

Actual results:
Deployment consistently fails

Expected results:
Deployment succeeds without errors

Additional info:


Note You need to log in before you can comment on or make changes to this bug.