If we have a few replicated suffixes on the single instance, they will use the one changelog ("cn=changelog5,%s" % DN_CONFIG).
If we disable the replication on the one of them by:
instance.replica.disableReplication(suffix=SUFFIX_2)
Then, according to the current logic, the changelog will be deleted. But it is still required by another replicated suffixes.
So if we want to avoid such problems, we should delete this block from lib389/replica.py:
407 # Delete the changelog 408 try: 409 self.conn.changelog.delete() 410 except ldap.LDAPError as e: 411 self.log.error('Failed to delete changelog: ' + e.message['desc']) 412 raise ldap.LDAPError
and handle the changelog deletion by executing changelog.delete() when we actually want this.
attachment 0001-Ticket-48318-Do-not-delete-a-changelog-while-disabli.patch
To ssh://git.fedorahosted.org/git/389/lib389.git
2917334..cf80a2a master -> master commit cf80a2a31d263ba5581aa57ac13f2744b21ede33 Author: Simon Pichugin spichugi@redhat.com Date: Wed Oct 21 14:24:23 2015 +0200
Milestone lib389 1.0 deleted
Metadata Update from @spichugi: - Issue assigned to spichugi
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/1649
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: Fixed)
Login to comment on this ticket.