The idea of a clone delegating part of its assigned range (current or next) to a new clone is, as we see from #3055 (see also PR: https://github.com/dogtagpki/pki/pull/40) a bit fraught. It would be better for the UpdateNumberRange servlet to create a full range assignment for the clone during creation. This probably requires some changes to the UpdateNumberRange API, but is otherwise a straightforward change. It should be implemented in a backwards compatible manner for a future release.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @ftweedal: - Issue set to the milestone: None (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @ftweedal: - Issue set to the milestone: 0.0 NEEDS_TRIAGE
See also: #619.
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/3178
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.