Bug 177473

Summary: ol-schema-migrate.pl generates mangled LDIF during Samba setup.
Product: [Retired] 389 Reporter: Brian Rudy <brudy>
Component: Database - GeneralAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED WORKSFORME QA Contact: Orla Hegarty <ohegarty>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: ohegarty, rmeggins
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-01-30 18:57:17 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:
Attachments:
Description Flags
Mangled 61samba.ldif
none
Original samba.schema none

Description Brian Rudy 2006-01-10 22:11:54 UTC
Description of problem:

While setting up FDS 1.0.1 as a LDAP backend for a Samba PDC (per the
Howto:Samba Wiki) the attached mangled 61samba.ldif was generated by
ol-schema-migrate.pl. Slapd does not complain about being unable to read the
schema file when loading, but attempting to load LDIFs with objectClasses
defined in 61samba.ldif fail with an 'Object class violation'.


Version-Release number of selected component (if applicable):

fedora-ds-1.0.1-1.RHEL3
14 June 2005 version of ol-schema-migrate.pl
RHEL ES 3
samba-3.0.9-1.3E.5

How reproducible:


Steps to Reproduce:
1. Download ol-schema-migrate.pl from
http://www.directory.fedora.redhat.com/download/ol-schema-migrate.pl
2. perl ol-schema-migrate.pl /usr/share/doc/samba-3.0.9/LDAP/samba.schema >
/opt/fedora-ds/slapd-<server>/config/schema/61samba.ldif
3. Create /tmp/sambaDomainName.ldif with the following content:

 dn: sambaDomainName=CMOMA,dc=cmoma,dc=mycompany,dc=com
 objectclass: sambaDomain
 objectclass: sambaUnixIDPool
 objectclass: top
 sambaDomainName: CMOMA
 sambaSID: S-1-5-21-4207250186-2406131440-3849861866
 uidNumber: 550
 gidNumber: 550 

4. /opt/fedora-ds/slapd-<server>/ldif2ldap "cn=Directory manager" password
/tmp/sambaDomainName.ldif



Actual results:

adding new entry sambaDomainName=CMOMA,dc=cmoma,dc=mycompany,dc=com
ldap_add: Object class violation
ldap_add: additional info: unknown object class "sambaUnixIDPool" 


Expected results:

Sucessful LDIF import.

Additional info:

Comment 1 Brian Rudy 2006-01-10 22:11:55 UTC
Created attachment 123017 [details]
Mangled 61samba.ldif

Comment 2 Rich Megginson 2006-01-10 23:25:30 UTC
Weird - I don't have this problem on my Fedora Core 4 system -
/usr/share/doc/samba-3.0.14a/LDAP/samba.schema

Can you attach your original samba.schema file?

Comment 3 Brian Rudy 2006-01-11 01:19:19 UTC
Created attachment 123023 [details]
Original samba.schema

This file was later used to generate a valid 61samba.ldif with the above
described procedure. I'm not sure why it behaved differently the first time.

Comment 4 Kevin Unthank 2006-01-30 18:57:17 UTC
Closing bug as not reproducable 
filed new bug 179379 to address problem with corrupt ldif errors
being silently ignored

Comment 5 Chandrasekar Kannan 2008-08-11 23:43:40 UTC
Bug already CLOSED. setting screened+ flag