#1549 Enabling random serial number management does not enable the same in clone
Closed: duplicate 6 years ago Opened 8 years ago by rpattath.

Enabling random serial number management does not enable the same in clone

Steps to Reproduce:

1. pkispawn master CA
2. pkispawn clone ca
3. Enable random serial number management through console of master CA

Actual results:

Random serial management is not enabled on clone CA even after waiting for a
while. Noticed ca.certStatusUpdateInterval=0 in clone CA's CS.cfg

Expected results:

Random serial management is expected to be enabled on clone after certificate
repository maintenance

commit d3d80046fd6985b809900005a685695d3181d9d3
commit de2c76f989adcf79b083c7f324c1b9b68571f83a

Fix may not be cherry-picked to every relevant branch.

Metadata Update from @rpattath:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

7 years ago

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue priority set to: 2 (was: 3)
- Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)

7 years ago

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.4.1-1.el7, pki-core-10.4.1-1.el7pki
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.4.1 (was: 10.4)
- Issue status updated to: Closed (was: Open)

6 years ago

Re-opened due to possible relation to "https://pagure.io/dogtagpki/issue/2557 - CA Cloning: Failed to update number range in few cases"

Metadata Update from @mharmsen:
- Custom field blockedby adjusted to https://pagure.io/dogtagpki/issue/2557
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.4 (was: 10.4.1)

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

6 years ago

Closing as DUPLICATE of https://pagure.io/dogtagpki/issue/2557 - CA Cloning: Failed to update number range in few cases

Metadata Update from @mharmsen:
- Issue close_status updated to: duplicate
- Issue set to the milestone: 10.5.0 (was: 10.5)
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.1 (was: 10.5.0)

6 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/2108

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.

Login to comment on this ticket.

Metadata