Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 .
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.
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 . 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.