+++ This bug is an upstream to downstream clone. The original bug is: +++
+++   bug 1721563 +++
======================================================================

Created attachment 1581752 [details]
engine.log

Description of problem:VM not started on the expected host since external weight policy units are ignored.


Version-Release number of selected component (if applicable):
ovirt-engine-4.3.4.3-0.1.el7.noarch

How reproducible: reproduced twice in automation runs. 
Also reproduced manually several times and Andrej looked at the env. 


Steps to Reproduce:
1. Install the package ovirt-scheduler-proxy on the engine.
2. Create the script /usr/share/ovirt-scheduler-proxy/plugins/filter_plugin.py on the engine
   Create the script /usr/share/ovirt-scheduler-proxy/plugins/weight_plugin.py on the engine
#!/bin/env python
class ExternalSchedulerWeightPlugin(object):
    def do_score(self, hosts, vm, args):
        hosts_scores = list()
        for host in hosts:
            if host == "fd9a906b-d88e-46ce-809a-2a22ab0495a5":
                continue
            hosts_scores.append((host, 50))
        print hosts_scores


   Create the script /usr/share/ovirt-scheduler-proxy/plugins/balance_plugin.py on the engine
   Create the script /usr/share/ovirt-scheduler-proxy/plugins/corrupted_plugin.py on the engine
   Create the script /usr/share/ovirt-scheduler-proxy/plugins/timeout_plugin.py on the engine
   Create the script /usr/share/ovirt-scheduler-proxy/plugins/stopped_plugin.py on the engine
3. Start the service ovirt-scheduler-proxy 
4. Enable the ovirt-scheduler-proxy via the engine config ('ExternalSchedulerEnabled=True')
5. Add new scheduling policy to the engine with {'name': 'weight_external_policy'} (screenshot attached external_weight_policy.png )
   Add the scheduling policy unit to the scheduling policy with {'unit_type': 'weight', 'unit_name': 'ExternalSchedulerWeightPlugin', 'policy_name': 'weight_external_policy'}
6. Run one VM 

Actual results: VM runs on host2 (not mentioned in plugin script)

Expected results:The tests expects the Vm to start on host1 (fd9a906b-d88e-46ce-809a-2a22ab0495a5).


Additional info: for QE. bug is reproduced on hosted-engine-04.lab.eng.tlv2.redhat.com
test rhevmtests.compute.sla.scheduler_tests.external_scheduler.external_scheduler_test.TestExternalSchedulerWeight

(Originally by Polina Agranat)