Created attachment 864007 [details] engine log Description of problem: Remove ovirt-scheduler-proxy external module failed with NullPointerException Version-Release number of selected component (if applicable): ovirt-scheduler-proxy-0.1.3-1.20140102.gitffebbc4.el6.noarch How reproducible: Always Steps to Reproduce: 1. Enable scheduler proxy via engine config 2. Add some new external module under /usr/share/ovirt-scheduler-proxy/plugins, it can be filter, score or balance function, run: service ovirt-scheduler-proxy restart && service ovirt-engine restart Chech that new module appear under Configure->Cluster Policies 3. Delete module from /usr/share/ovirt-scheduler-proxy/plugins and run service ovirt-scheduler-proxy restart && service ovirt-engine restart, try to remove module under Configure->Cluster Policies->Manage Policy Units Actual results: Remove failed, with java NullPointerException in engine.log Expected results: Module must removed Additional info:
Also if you have some module for example max_vms_filter.py under /usr/share/ovirt-scheduler-proxy/plugins and edit file and change name of class from max_vms to max_vms_1 under Manage Policy Units I see two filters one that disabled max_vms and one enabled max_vms_1(also it happening after service ovirt-scheduler-proxy restart && service ovirt-engine restart).
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
changed TR to 3.4.1. if this is needed for 3.4.0, it needs to be backported to 3.4.0 branch as well
This is an automated message oVirt 3.4.1 has been released: * should fix your issue * should be available at your local mirror within two days. If problems still persist, please make note of it in this bug report.