Bug 1384428

Summary: Not possible to create acl group and acl user with same names.
Product: Red Hat Enterprise Linux 8 Reporter: Ondrej Mular <omular>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED WONTFIX QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: medium    
Version: ---CC: cfeist, cluster-maint, idevat, omular, tojeline
Target Milestone: pre-dev-freezeKeywords: Reopened, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-12 07:28:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1384420    
Bug Blocks:    

Description Ondrej Mular 2016-10-13 09:23:30 UTC 
Description of problem:
It is not possible to create acl group and acl user with same names. Also name of user/group cannot be the same as for example resource.

Version-Release number of selected component (if applicable):
[root@rhel72-node5 ~]# rpm -q pcs
pcs-0.9.143-15.el7.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Create acl user:
[root@rhel72-node5 ~]# pcs acl user create testname
2. Try to add group with same name as user to the acl configuration:
[root@rhel72-node5 ~]# pcs acl group create testname
Error: testname already exists

Actual results:
It is not possible to create user and group with same name.

Expected results:
It should be possible to create user and group with same name.
Comment 6 RHEL Program Management 2020-11-01 03:03:06 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 7 Tomas Jelinek 2022-12-12 10:17:26 UTC 
Reopening for consideration as this has been recently implemented in pacemaker (feature set 3.16.1).
Comment 10 RHEL Program Management 2023-06-12 07:28:11 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.