RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 689810 - Inconsistent Error message attempting to add duplicate user
Summary: Inconsistent Error message attempting to add duplicate user
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
low
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-22 14:06 UTC by Jenny Severance
Modified: 2015-01-04 23:47 UTC (History)
3 users (show)

Fixed In Version: ipa-2.1.0-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: Adding a duplicate user resulted in a generic error message. Consequence: The error message itself was not specific enough to tell you exactly what was wrong. Fix: Include the object type and primary key in the error message. In this case the fact that a user with login xyz already exists. Result: A more consistent, understandable error message is presented.
Clone Of:
Environment:
Last Closed: 2011-12-06 18:21:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1533 0 normal SHIPPED_LIVE Moderate: ipa security and bug fix update 2011-12-06 01:23:31 UTC

Description Jenny Severance 2011-03-22 14:06:24 UTC
Description of problem:
I thought this bug was already logged but I can't find it.  Sorry if it is a duplicate.


::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: ipa-user-cli-add-003: Add Duplicate User
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [09:21:36] ::  Executing: ipa user-add --first=Superuser --last=crazylastnametoolong sup34
ipa: ERROR: This entry already exists
:: [09:21:38] ::  "ipa user-add --first=Superuser --last=crazylastnametoolong sup34" failed as expected.
:: [09:21:40] ::  ERROR: Message not as expected. GOT: ipa: ERROR: This entry already exists  EXP: ipa: ERROR: user with name sup34 already exists


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

How reproducible:
alwayas

Steps to Reproduce:
1. add a new user
2. try to add the same user
3.
  
Actual results:


Expected results:
 ipa: ERROR: This entry already exists

Additional info:
ipa: ERROR: user with name sup34 already exists

Comment 2 Dmitri Pal 2011-03-22 14:16:00 UTC
https://fedorahosted.org/freeipa/ticket/1116

Comment 3 Rob Crittenden 2011-03-22 14:18:31 UTC
Do I understand correctly that you are requesting a LESS-specific error message?

This would revert the following bugs (from ticket https://fedorahosted.org/freeipa/ticket/530)

https://bugzilla.redhat.com/show_bug.cgi?id=655994

https://bugzilla.redhat.com/show_bug.cgi?id=656001 

Or do you want less information only for users?

Comment 4 Jenny Severance 2011-03-22 14:28:28 UTC
sorry ... mixed that up ... no want the error message to be consistent with all the other  CLIs and report  "ipa: ERROR: user with name sup34 already exists"

Comment 5 Martin Kosek 2011-03-30 06:40:08 UTC
Fixed in 67a29028160e129c3cf486b6caa1333f0d237596.

Comment 8 Jenny Severance 2011-07-19 19:29:43 UTC
verified:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: ipa-user-cli-add-003: Add Duplicate User
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [10:37:32] ::  Executing: ipa user-add --first=Superuser --last=crazylastnametoolong sup34
ipa: ERROR: user with name "sup34" already exists
:: [10:37:34] ::  "ipa user-add --first=Superuser --last=crazylastnametoolong sup34" failed as expected.
:: [10:37:35] ::  Error message as expected: ipa: ERROR: user with name sup34 already exists
:: [   PASS   ] :: Verify expected error message.
'102c97d5-1a91-423d-9aa8-36ce8265abf7'
ipa-user-cli-add-003 result: PASS


version:

ipa-server.x86_64 0:2.0.99-3.20110719T0529zgit824ec7e.el6

Comment 9 Rob Crittenden 2011-10-31 16:18:21 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:
Cause: Adding a duplicate user resulted in a generic error message.
Consequence: The error message itself was not specific enough to tell you exactly what was wrong.
Fix: Include the object type and primary key in the error message. In this case the fact that a user with login xyz already exists.
Result: A more consistent, understandable error message is presented.

Comment 10 errata-xmlrpc 2011-12-06 18:21:00 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/RHSA-2011-1533.html


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