This bug is needed for the errata process. +++ This bug was initially created as a clone of Bug #1346252 +++ Description of problem: Mom will be doing nothing for VMs that have no IO QoS defined Mom logs, reports missing fields for the vm: Incomplete data: missing set(['io_tune_current', 'io_tune']) Version-Release number of selected component (if applicable): mom-0.5.4-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Run VM with guest agent 2. check mom logs, if you get: getVmBalloonInfo() is not ready ->> then the VM is not ready and no policy will be evaluated on it 3. Actual results: Expected results: Additional info: --- Additional comment from Martin Sivák on 2016-06-14 13:48:14 CEST --- We need to create GuestIoTuneOptional collector in MOM and then use it in VDSM's configuration file for MOM. --- Additional comment from Roy Golan on 2016-06-15 08:00:27 CEST --- Is the evaluation of policy is such inclusive? isn't it triggered with minimum requirements? If not it should be --- Additional comment from Martin Sivák on 2016-06-15 10:21:28 CEST --- (In reply to Roy Golan from comment #2) > Is the evaluation of policy is such inclusive? isn't it triggered with > minimum requirements? If not it should be Uh? That is the whole point of this bug. The currently used GuestIoTune adds the io_tune variables to the list of required values. --- Additional comment from Doron Fediuck on 2016-06-20 10:26:01 CEST --- --- Additional comment from Red Hat Bugzilla Rules Engine on 2016-06-20 10:59:19 CEST --- This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Is this really MODIFIED? Where the the backports?
Yes this is modified, mom-0.5.5 has been in brew for weeks and we tagged it for 3.6 this week.
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://rhn.redhat.com/errata/RHBA-2016-1508.html