+++ This bug was initially created as a clone of Bug #1518541 +++ Description of problem: VDO thin provisioning will need to be monitored (physical space) ( sysfs) Alerts (optionally to UI, SMTP, system logs) to be sent that more physical space is needed or the storage admin needs to consider removing unneeded data proposed Alert levels are: Notify: that more free space is needed (80%, but not less than 2TB) Warn: that system is near full (90%, but not less than 1TB) Critical: the VMs should be paused and / or file system should be put into read-only mode (95%, but not less than 500GB ) ON DEMAND via the UI reporting of space savings / physical space to be included (including exposed in Cockpit) How reproducible: NA
The latest build doesn't contain the changes. Dev team is making efforts to deliver the private rpm, so that the functionality of the feature could be tested. So far QE tried installing couple of rpms from Denis, and those are upstream rpms and has conflicts with downstream packages available in RHVH
As the build containing the fixes is not yet available moving the state of the bug to MODIFIED
The dependent bug is not yet ON_QA, moving the RHHI bug to ASSIGNED
Verified the bug in ovirt-engine-4.2.5.2. Steps: ===== 1.Create a vdo based storage domain 2.Create a volume of size 899GB 3.Set the "warning low space indicator" to 98 and "warning low confirmed space indicator" to 97 4.Saw the alerts which it reached that point Logs from HE: ============ 2018-07-26 11:11:30,848+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-79) [] EVENT_ID: IRS_DISK_SPACE_LOW_ERROR(201), Critical, Low disk space. vdo_sdd domain has 879 GB of free space. 2018-07-26 11:11:10,692+05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-79) [] EVENT_ID: IRS_DISK_SPACE_LOW(26), Warning, Low disk space. vdo_sdd domain has 881 GB of free space.
Apologies from changing the state to NEW. Reverting back as verified
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, 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/RHEA-2018:3523