... [7/10]: upgrading server Add failure missing attribute "nsSystemIndex" required by object class "nsIndex" [8/10]: stopping directory server ...
entries in 20-indicies.update have missing nsSystemIndex
dn: cn=ntUniqueId,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config default:cn: ntUniqueId default:ObjectClass: top default:ObjectClass: nsIndex only:nsIndexType: eq only:nsIndexType: pres dn: cn=ntUserDomainId,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config default:cn: ntUserDomainId default:ObjectClass: top default:ObjectClass: nsIndex only:nsIndexType: eq only:nsIndexType: pres
The same entries in have missing nsSystemIndex in indices.ldif, but there it somehow works
My suspicion over the different behavior of the .update and .ldif files with the LDAP entries is that in the .ldif file the modify action does not touch the objectClass of the given attributes whereas in the .update file it does.
master:
Metadata Update from @mbasti: - Issue assigned to stlaz - Issue set to the milestone: FreeIPA 4.4
Login to comment on this ticket.