#618 Cloning a cloned CA creates replica ID range not in sequence with original ID range
Closed: migrated 3 years ago by dmoluguw. Opened 10 years ago by awnuk.

Cloning a cloned CA creates replica ID range not in sequence with original ID range.[[BR]]
[[BR]]

Step 1. Clone original CA:

Original CA after cloning:

grep ^dbs pki-ca/conf/CS.cfg | grep -i replica

dbs.beginReplicaNumber=1
dbs.endReplicaNumber=95
dbs.replicaCloneTransferNumber=5
dbs.replicaDN=ou=replica
dbs.replicaIncrement=100
dbs.replicaLowWaterMark=20
dbs.replicaRangeDN=ou=replica, ou=ranges

Cloned CA:

grep ^dbs pki-ca-clone1/conf/CS.cfg | grep -i replica

dbs.beginReplicaNumber=98
dbs.endReplicaNumber=100
dbs.replicaCloneTransferNumber=5
dbs.replicaDN=ou=replica
dbs.replicaIncrement=100
dbs.replicaLowWaterMark=20
dbs.replicaRangeDN=ou=replica, ou=ranges

[[BR]]

Step 2. Clone a cloned CA

Cloned CA after cloning:

grep ^dbs pki-ca-clone1/conf/CS.cfg | grep -i replica

dbs.beginReplicaNumber=98
dbs.endReplicaNumber=100
dbs.nextBeginReplicaNumber=1000
dbs.nextEndReplicaNumber=1094
dbs.replicaCloneTransferNumber=5
dbs.replicaDN=ou=replica
dbs.replicaIncrement=100
dbs.replicaLowWaterMark=20
dbs.replicaRangeDN=ou=replica, ou=ranges

Clone of a cloned CA:

grep ^dbs pki-ca-clone2/conf/CS.cfg | grep -i replica

dbs.beginReplicaNumber=1096
dbs.endReplicaNumber=1099
dbs.replicaCloneTransferNumber=5
dbs.replicaDN=ou=replica
dbs.replicaIncrement=100
dbs.replicaLowWaterMark=20
dbs.replicaRangeDN=ou=replica, ou=ranges

Metadata Update from @awnuk:
- Issue set to the milestone: UNTRIAGED

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1188

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, and we apologize for any inconvenience.

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

3 years ago

Login to comment on this ticket.

Metadata