Description of problem: Let's say the storage domain size is 2047G. Via Webadmin->manage domain window -> change 'Critical space action blocker' to more than the SD size, for example, 3000G -> this is allowed. So it's possible to insert a number bigger than storage domain size which does not make sense to me & the system accept this & blocks actions on that SD. Critical space action blocker value should not be more than the maximum size of the storage domain. Version-Release number of selected component (if applicable): 4.2.1-0.2.el7 How reproducible: 100% Steps to Reproduce: 1.Via Webadmin->manage domain window -> change 'Critical space action blocker' to more than the SD size, for example, 3000G Actual results: Critical space action blocker value can be more than the maximum size of the storage domain. Expected results: Critical space action blocker value should not be more than the maximum size of the storage domain. Additional info:
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Verified ovirt-engine-4.3.6-0.1.el7.noarch vdsm-4.30.25-1.el7ev.x86_64
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.