Created attachment 2009008 [details] Mon count configure modal Description of problem (please be detailed as possible and provide log snippests): When the cluster has 5 or more failure domain/zones, a `CephMonLowNumber` alert is shown to the user with a "Configure" option. After clicking the "Configure" option a modal pops up that has the recommended mon count value and the current mon count value, and the current value is blank/undefined in the modal. Version of all relevant components (if applicable): 4.15 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: No Steps to Reproduce: 1. Create a 5 node cluster with 5 failure domains/zones. 2. The "CephMonLowNumber" alert will be fired once ODF is installed successfully. 3. Try to configure the mon count from the alert, you will see a blank value for the "Monitor Count" field. Actual results: The current mon count value is not shown in the configure modal. Expected results: The current mon count value should be shown in the configure modal. Additional info: N.A
Verified with OCP 4.15 and ODF 4.15.0-130 Verification steps: 1. Created a 5 node cluster with 5 failure domains/zones. 2. The "CephMonLowNumber" alert was fired once ODF was installed successfully. 3. Upon Trying to configure the mon count from the alert, In Configure Ceph Monitor tab current mon count value is displayed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:1383