Description of problem (please be detailed as possible and provide log snippests): Once creating a new StorageProfile with blank or removed DeviceClass, editing its fields (namely DeviceClass, but this also applies to the rest of the fields as they're marked with Optional) is enabled. Version of all relevant components (if applicable): 4.14-stable 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? The solution is to adjust the validation rules to guarantee immutability at all times. 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? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1.Create a StroageProfile CR with a blank sub-field 2.Edit it to include that sub-field's value Actual results: The changes will be applied w/o errors Expected results: Changes should not be applied and an error needs to be displayed. Additional info:
Created attachment 2001946 [details] Sample StorageProfile CR
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