| Summary: | Backend: Non 3.1 clusters Failed to add network via REST API if doesn't include VM network config | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Avi Tal <atal> |
| Component: | ovirt-engine-core | Assignee: | Roy Golan <rgolan> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | acathrow, dyasny, iheim, mgoldboi, oliel, srevivo, ykaul |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 3.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-09 07:56:29 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: | |
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 closing ON_QA bugs as oVirt 3.1 was released: http://www.ovirt.org/get-ovirt/ |
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.]