Bug 741604 - misleading error when adding duplicate external members to sudo rule
Summary: misleading error when adding duplicate external members to sudo rule
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: 756082
TreeView+ depends on / blocked
 
Reported: 2011-09-27 12:28 UTC by Namita Soman
Modified: 2013-12-16 16:50 UTC (History)
5 users (show)

Fixed In Version: ipa-2.2.0-1.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed.
Clone Of:
Environment:
Last Closed: 2012-06-20 13:14:14 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0819 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2012-06-19 20:34:17 UTC

Description Namita Soman 2011-09-27 12:28:53 UTC
Description of problem:
Running the command below more than once:
ipa sudorule-add-user --users=user1,user2 SudoRule1
where user1 is an IPA user, and user2 is an external user
gives different errors for the two users.

For the IPA user - error is - 
member user: user1: This entry is already a member
but for the external user, error is -
member user: user2: no such entry

Version-Release number of selected component (if applicable):
ipa-server-2.1.1-4.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Add User user1, and a sudo rule SudoRule1
2. Run: ipa sudorule-add-user --users=user1,user2 SudoRule1
3. Run the command again

  
Actual results:
indicates user1 is already a member, but for user2 - that "no such entry"

Expected results:
indicate both users are members already

Additional info:
This is the error thrown in UI as well, and can be confusing.

Comment 2 Martin Kosek 2011-09-27 13:04:01 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/1884

Comment 5 Steeve Goveas 2012-04-10 14:59:00 UTC
[root@wheeljack ~]# ipa user-add user1 --first user1 --last ping
------------------
Added user "user1"
------------------
  User login: user1
  First name: user1
  Last name: ping
  Full name: user1 ping
  Display name: user1 ping
  Initials: up
  Home directory: /home/user1
  GECOS field: user1 ping
  Login shell: /bin/sh
  Kerberos principal: user1.PNQ.REDHAT.COM
  UID: 1956600001
  GID: 1956600001
  Password: False
  Kerberos keys available: False

[root@wheeljack ~]# ipa sudorule-add Sudorule1
---------------------------
Added Sudo Rule "Sudorule1"
---------------------------
  Rule name: Sudorule1
  Enabled: TRUE

[root@wheeljack ~]# ipa sudorule-add-user --users=user1,user2 Sudorule1
  Rule name: Sudorule1
  Enabled: TRUE
  Users: user1
  External User: user2
-------------------------
Number of members added 2
-------------------------

[root@wheeljack ~]# ipa sudorule-add-user --users=user1,user2 Sudorule1
  Rule name: Sudorule1
  Enabled: TRUE
  Users: user1
  External User: user2
  Failed users/groups: 
    member user: user1: This entry is already a member
    member user: user2: This entry is already a member
    member group: 
-------------------------
Number of members added 0
-------------------------
[root@wheeljack ~]#

Output gives expected result. Verified in version ipa-server-2.2.0-8.el6.x86_64

Comment 6 Martin Kosek 2012-04-18 20:07:51 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed.

Comment 8 errata-xmlrpc 2012-06-20 13:14:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0819.html


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