Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1939284

Summary: clusterPolicyWeightFunctionInfo tooltip needs improvement in relation to Rank Selector policy unit.
Product: Red Hat Enterprise Virtualization Manager Reporter: Germano Veit Michel <gveitmic>
Component: ovirt-engineAssignee: Milan Zamazal <mzamazal>
Status: CLOSED ERRATA QA Contact: Polina <pagranat>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4.4CC: ahadas, audgiri, dfodor, imomin, mavital, mzamazal, sgratch, shipatil
Target Milestone: ovirt-4.5.2Keywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.5.2 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-08 11:28:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Germano Veit Michel 2021-03-15 23:18:40 UTC 
Description of problem:

The tooltip in Administration -> Configure -> Scheduling Policies -> Weights Modules seems a bit out of date. It appears to describe the WeightSelector Policy Unit instead of the newer (and default) Rank Selector policy unit.

clusterPolicyWeightFunctionInfo=Weights represent soft constraints for running a VM. Note\: in a weighting system, lower score is considered better. So a host with the lowest score (weight) is the one the scheduler will choose. Each weight module scores any given host based on an optimization logic the module implements. For example, if we want to optimize for CPU load, the module will score each host based on its known CPU load. Weight modules scores are being summed, so it is possible to have more than one weight module. The way to prioritize modules is by increasing / decreasing a factor.

Can this be improved to explain that the scores are ranked, and then the host with lowest accumulated rank wins? I think it would be more in line to what actually happens.

Version-Release number of selected component (if applicable):
Same text even on master branch

How reproducible:
Always

Steps to Reproduce:
1. Go to  Administration -> Configure -> Scheduling Policies -> Weights Modules and see tooltip
Comment 7 Milan Zamazal 2022-07-19 15:53:48 UTC 
Germano, you can check the updated text at https://github.com/oVirt/ovirt-engine/pull/534 if you like.
Comment 8 Germano Veit Michel 2022-07-19 21:14:19 UTC 
(In reply to Milan Zamazal from comment #7)
> Germano, you can check the updated text at
> https://github.com/oVirt/ovirt-engine/pull/534 if you like.

Thanks Milan, it looks correct now.
Comment 9 meital avital 2022-07-20 07:24:02 UTC 
Due to QE capacity we are not going to cover this issue in our automation
Comment 12 Polina 2022-07-26 10:35:43 UTC 
verified on ovirt-engine-4.5.2-0.3.el8ev.noarch
Comment 16 errata-xmlrpc 2022-09-08 11:28:54 UTC 
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: RHV Manager (ovirt-engine) [ovirt-4.5.2] bug fix and security 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-2022:6393