Description of problem: Datacenter admin can't change the interval of Affinity Rules Enforcement Manager. Steps to Reproduce: 1. Change interval of AREM using engine-config to 5 minutes 2. Run engine (Using share/ovirt-engine/services/ovirt-engine/ovirt-engine.py start) Expected results: 1. AREM will run after 5 minutes instead of 1.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
Please explain which config key should be used and what AREM is.
config key that should be used: AffinityRulesEnforcementManagerRegularInterval can be changed to 5 minutes by typing in the shell from the root directory of oVirt: bin/engine-config -s AffinityRulesEnforcementManagerRegularInterval=5 AREM, as stated in the "description of problem" stands for Affinity Rules Enforcement Manager. It is a manager which is responsible for enforcing VM affinity.
This bug has target milestone 3.6.2 and is on modified without a target release. This may be perfectly correct, but please check if the patch fixing this bug is included in ovirt-engine-3.6.2. If it's included, please set target-release to 3.6.2 and move to ON_QA. Thanks.
Added some patches. This should stay in POST until all bugs will be merged.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Why did you remove me from the bug?
(In reply to Tomer Saban from comment #7) > Why did you remove me from the bug? Sorry, unwanted change while mass moving target to 3.6.2.5
Checked on rhevm-backend-3.6.2.5-0.1.el6.noarch [root@alukiano-rhevm-36 ~]# engine-config -g AffinityRulesEnforcementManagerRegularInterval AffinityRulesEnforcementManagerRegularInterval: 1 version: general [root@alukiano-rhevm-36 ~]# engine-config -s AffinityRulesEnforcementManagerRegularInterval=5 [root@alukiano-rhevm-36 ~]# engine-config -g AffinityRulesEnforcementManagerRegularInterval AffinityRulesEnforcementManagerRegularInterval: 5 version: general I see that engine not apply correct interval on first AREM run. 016-01-21 11:29:37,153 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ServerService Thread Pool -- 50) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Affinity Rules Enforcement Manager started. 2016-01-21 11:30:37,156 DEBUG [org.ovirt.engine.core.bll.scheduling.AffinityRulesEnforcementManager] (DefaultQuartzScheduler_Worker-26) [] Affinity Rules Enforcement Manager interval reached. 2016-01-21 11:35:37,808 DEBUG [org.ovirt.engine.core.bll.scheduling.AffinityRulesEnforcementManager] (DefaultQuartzScheduler_Worker-57) [] Affinity Rules Enforcement Manager interval reached. 2016-01-21 11:40:37,835 DEBUG [org.ovirt.engine.core.bll.scheduling.AffinityRulesEnforcementManager] (DefaultQuartzScheduler_Worker-64) [] Affinity Rules Enforcement Manager interval reached. I do not think it is some serous problem with that, but Tomer can you approve that it is desired behavior?
That's OK. That's the desired behaviour. The initial message is for the initialization of the Affinity Rules Enforcement Manager and then, we want the it start the regular process regardless of the interval. So it will commence after 1 minute of the initialization.
Verified on rhevm-backend-3.6.2.5-0.1.el6.noarch