Set up freeipa on F20 using 1.3.2. The errors log on the 2nd master is full of messages like these:
[16/Dec/2013:14:37:24 -0500] NSMMReplicationPlugin - Schema agmt="cn=meToServer1" (Server1:389) must not be overwritten (set replication log for additional info) [16/Dec/2013:14:37:24 -0500] NSMMReplicationPlugin - agmt="cn=meToServer1" (Server1:389): Warning: unable to replicate schema: rc=1
I'm not really reproducing this using:
389-ds-base-1.3.2.9-1.fc20.x86_64 freeipa-server-3.3.3-4.fc20.x86_64
I do get ~13 errors during the install, but it resolves itself, and then they no longer appear:
{{{ [04/Feb/2014:14:45:44 -0500] schema - Attribute mail is not required in 'mailGroup' of the local supplier schema [04/Feb/2014:14:45:44 -0500] schema - Attribute ipaKrbAuthzData is not allowed in 'ipaGuiConfig' of the local supplier schema [04/Feb/2014:14:45:45 -0500] NSMMReplicationPlugin - Schema agmt="cn=meToServer" (server:389) must not be overwritten (set replication log for additional info) [04/Feb/2014:14:45:45 -0500] NSMMReplicationPlugin - agmt="cn=meToServer" (dell-pe1950-02:389): Warning: unable to replicate schema: rc=1
<the sequence above repeats 12 more times> ... ... [04/Feb/2014:14:50:03 -0500] NSMMReplicationPlugin - Schema checking successful: ok to push the schema (agmt="cn=meToServer" (server:389)) }}}
This appears to resolve itself during one of the IPA install phases that applies the LDAP updates, which updates the schema(99user.ldif) and addresses the schema issues in the error log.
Is this the same behavior seen when the ticket was filed? Or was it much worse, and never it resolved itself?
ok, then perhaps it was fixed by some other update in 389 or IPA
May we close this bug?
Closing ticket
Metadata Update from @nhosoi: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.2.12
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/970
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.