389-ds-base

#49657 Make the cascading replication scenario work with existing replica lib389 API
Closed: wontfix Opened by spichugi.

Closed: wontfix
Reopen Issue

We should be able to create cascading replication topology with existing lib389 API.
Fix existing topology in topologies.py and add the functionality to replica.py API accordingly.

@spichugi I think I took this into account in the new replmanager class. I just don't think I actually got about to testing it fully.

Metadata Update from @firstyear:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

Metadata Update from @spichugi:
- Custom field reviewstatus adjusted to review (was: None)

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to ack (was: review)

afb755bd9..50732c9e8 master -> origin/master

Metadata Update from @spichugi:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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/2716

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)
Metadata
None
None
None
None
ack
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.