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

Bug 1114955

Summary: Add filter, weight or balance module under cluster policy failed
Product: [Retired] oVirt Reporter: Artyom <alukiano>
Component: ovirt-engine-apiAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5CC: acathrow, gklein, iheim, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-01 11:35:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Artyom 2014-07-01 10:42:03 UTC
Description of problem:
When I trying to add new filter under cluster policy action failed

Version-Release number of selected component (if applicable):
ovirt-engine-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Add new filter under user cluster policy via REST(https://engine_ip/api/schedulingpolicies/scheduling_policy_id/filters)
2. Run post request with: <filter id="id_of_one_of_available_filters"/>
3.

Actual results:
Action failed with error:
HTTP Status 500 - Bad arguments passed to public abstract org.ovirt.engine.api.model.BaseResource org.ovirt.engine.api.resource.PolicyUnitsResource.add(org.ovirt.engine.api.model.BaseResource) ( org.ovirt.engine.api.model.Filter org.ovirt.engine.api.model.Filter@20c69f3a )

Expected results:
Action success without any errors

Additional info:
The same thing also relevant for weight and balancing modules

Comment 1 Juan Hernández 2014-07-01 11:35:13 UTC
This is a duplicate of bug 1113485. As a workaround use /ovirt-engine/api instead of /api.

*** This bug has been marked as a duplicate of bug 1113485 ***