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:
Created attachment 123017 [details] Mangled 61samba.ldif
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?
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.
Closing bug as not reproducable filed new bug 179379 to address problem with corrupt ldif errors being silently ignored
Bug already CLOSED. setting screened+ flag