Bug 1290456

Summary: sssd: [sysdb_add_user] (0x0400): Error: 17 (File exists)
Product: Red Hat Enterprise Linux 6 Reporter: Jan Kurik <jkurik>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.8CC: akasurde, ekeck, grajaiya, jhrozek, jkurik, kbanerje, ksiddiqu, lslebodn, mkosek, mnavrati, mzidek, nsoman, pbrezina, preichl, sbose, sgoveas, sssd-maint, sumenon
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: sssd-1.12.4-47.el6_7.5 Doc Type: Bug Fix
Doc Text:
Previously, after using the ipa-winsync-migrate command to migrate users from WinSync to the Identity Management (IdM) trust solution, retrieving an Active Directory (AD) user failed. Also, the SSSD debugging logs contained the following error message: [sysdb_add_user] (0x0400): Error: 17 (File exists) A patch has been applied to address this bug. As a result, AD users are retrieved as expected, and the error no longer occurs in the described situation.
Story Points: ---
Clone Of: 1285852 Environment:
Last Closed: 2016-02-09 09:04:31 UTC Type: ---
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: 1285852    
Bug Blocks:    
Attachments:
Description Flags
console.log none

Description Jan Kurik 2015-12-10 15:08:36 UTC
This bug has been copied from bug #1285852 and has been proposed
to be backported to 6.7 z-stream (EUS).

Comment 4 Abhijeet Kasurde 2016-01-21 11:29:40 UTC
Created attachment 1116913 [details]
console.log

Comment 5 Abhijeet Kasurde 2016-01-21 11:30:32 UTC
Verified using sssd version - 	sssd-1.12.4-47.el6_7.7.x86_64

Attached console.log

Comment 7 errata-xmlrpc 2016-02-09 09:04:31 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-0153.html