Description of problem:
Code throws java.io.IOException: Error: Failed to update number range. in certain use cases.
For reproducing this error , I did some changes in CS.cfg because it might not be possible in regular test cases to reproduce it.Hence some small hacks are needed to generate it.
Version-Release number of selected component (if applicable): RHEL 7.7
How reproducible: always
Steps to Reproduce: 1. Install master . topology-02-CA. 2. Do below changes in CS.cfg dbs.beginSerialNumber=1 dbs.endSerialNumber=30 dbs.serialCloneTransferNumber=8 dbs.serialIncrement=100 dbs.serialLowWaterMark=6 Restart master .
dbs.beginSerialNumber=1 dbs.endSerialNumber=30 dbs.serialCloneTransferNumber=8 dbs.serialIncrement=100 dbs.serialLowWaterMark=6
3. Install clone . topology-02-CA-clone.
Actual results:
Getting error ; https://bugzilla.redhat.com/show_bug.cgi?id=1754845#c9
Expected results:
It should not result in such errors and NPE. NPE and stack trace never looks user friendly.
Additional info:
Refer bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1754845#c9 for detailed scenario and use cases.
https://bugzilla.redhat.com/show_bug.cgi?id=1774928
Metadata Update from @cipherboy: - 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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1774928 - Custom field type adjusted to None - Custom field version adjusted to None
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/3282
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.