Hide Forgot
Failed to add network to non 3.1 cluster if rest element doesn't include VM network configurations. POST: <network id='...'> <name>testrest1</name> <data_center id='...'/> <stp>false</stp> <status><state>non_operational</state></status> </network> response: <fault> <reason>Operation Failed</reason> <detail>[Non VM networks is not supported for this for this (compatibility) version of Data Center.]</detail> </fault> Solution: Should have default value of True for VM networks. Note: this CanDoAction has a typo of duplicate "for this" [Non VM networks is not supported for this for this (compatibility) version of Data Center.]
Did it work before adding the 'VM network' feature? If it did, it's a regression - please mark it as such.
The parameter should either be mandatory in REST-API, but only if business logic justifies this, or it should get a default value in the Backend - IMO
http://gerrit.ovirt.org/#change,3556
closing ON_QA bugs as oVirt 3.1 was released: http://www.ovirt.org/get-ovirt/