Ticket #618 shows CA, it's clone (ca-clone1), and clone of the clone (ca-clone2). Respective configuration information is included below.[[BR]]
Cloning a CA clone (ca-clone1) for the second time, transfers replica IDs from nextReplica range instead of current replica range.
Cloned CA after first 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
Cloned CA after second cloning:
grep ^dbs pki-ca-clone1/conf/CS.cfg | grep -i replicadbs.beginReplicaNumber=98 dbs.endReplicaNumber=100 dbs.nextBeginReplicaNumber=1000 dbs.nextEndReplicaNumber=1089 dbs.replicaCloneTransferNumber=5 dbs.replicaDN=ou=replica dbs.replicaIncrement=100 dbs.replicaLowWaterMark=20 dbs.replicaRangeDN=ou=replica, ou=ranges
Second clone of a cloned CA:
grep ^dbs pki-ca-clone3/conf/CS.cfg | grep -i replica dbs.beginReplicaNumber=1091 dbs.endReplicaNumber=1094 dbs.replicaCloneTransferNumber=5 dbs.replicaDN=ou=replica dbs.replicaIncrement=100 dbs.replicaLowWaterMark=20 dbs.replicaRangeDN=ou=replica, ou=ranges
[[BR]] [[BR]]
Ticket #618 information:
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:
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
Result of testing for ticket #325.
Cloning of ca-clone3 results in similar use of next replica range instead of current range.
ca-clone3 before cloning:
ca-clone3 after cloning:
grep ^dbs pki-ca-clone3/conf/CS.cfg | grep -i replica dbs.beginReplicaNumber=1091 dbs.endReplicaNumber=1094 dbs.nextBeginReplicaNumber=1100 dbs.nextEndReplicaNumber=1194 dbs.replicaCloneTransferNumber=5 dbs.replicaDN=ou=replica dbs.replicaIncrement=100 dbs.replicaLowWaterMark=20 dbs.replicaRangeDN=ou=replica, ou=ranges
ca-clone4 clone of ca-clone3:
grep ^dbs pki-ca-clone4/conf/CS.cfg | grep -i replica dbs.beginReplicaNumber=1196 dbs.endReplicaNumber=1199 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
Closing this as a duplicate of #3060.
Metadata Update from @cipherboy: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
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/1189
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, and we apologize for any inconvenience.
Login to comment on this ticket.