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 1285852 - sssd: [sysdb_add_user] (0x0400): Error: 17 (File exists)
Summary: sssd: [sysdb_add_user] (0x0400): Error: 17 (File exists)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.8
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On: 1283592
Blocks: 1284814 1290456
TreeView+ depends on / blocked
 
Reported: 2015-11-26 16:41 UTC by Jakub Hrozek
Modified: 2020-05-04 10:52 UTC (History)
16 users (show)

Fixed In Version: sssd-1.13.2-4.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1283592
: 1290456 (view as bug list)
Environment:
Last Closed: 2016-05-10 20:25:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
sssd logs (40.81 KB, text/plain)
2016-03-02 08:43 UTC, Sudhir Menon 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 3915 0 None closed sssd: [sysdb_add_user] (0x0400): Error: 17 (File exists) 2021-01-15 08:44:07 UTC
Red Hat Product Errata RHBA-2016:0782 0 normal SHIPPED_LIVE sssd bug fix and enhancement update 2016-05-10 22:36:00 UTC

Comment 7 Sudhir Menon 2016-03-02 08:42:50 UTC 
Verified the bug using  

RHEL6.8 client
ipa-client-3.0.0-50.el6.x86_64
sssd-ipa-1.13.3-15.el6.x86_64

RHEL7.2 IPA Server
ipa-server-4.2.0-15.el7_2.3.x86_64
sssd-1.13.0-40.el7_2.1.x86_64

Observations:-
1. when you run 'id username' command on the IPA server first and then run it on IPA client, the 'id username' command displays output on the ipaclient.
2. 'no such user' is displayed if the 'id username' command is run on the ipaclient first. Is this expected ? 

Attaching the logs for reference which shows 'Error 17' when the id command is run on client.
Comment 8 Sudhir Menon 2016-03-02 08:43:53 UTC 
Created attachment 1132172 [details]
sssd logs
Comment 10 Sudhir Menon 2016-03-03 10:51:33 UTC 
Observations:-

After running the below command on IPA-Server and IPA-client, the issue mentioned in comment #7 is not seen. Also Error 17 is not seen in the logs.

#service sssd stop; rm -rf /var/lib/sss/{db,mc}/*; service sssd start

RHEL6.8 client
ipa-client-3.0.0-50.el6.x86_64
sssd-ipa-1.13.3-15.el6.x86_64

RHEL7.2 IPA Server
ipa-server-4.2.0-15.el7_2.3.x86_64
sssd-1.13.0-40.el7_2.1.x86_64
Comment 12 errata-xmlrpc 2016-05-10 20:25: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.

https://rhn.redhat.com/errata/RHBA-2016-0782.html
Note You need to log in before you can comment on or make changes to this bug.