Bug 834198
Summary: | OVIRT-CLI: update network by name doesn't work | ||
---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Elena <edolinin> |
Component: | ovirt-engine-cli | Assignee: | Michael Pasternak <mpastern> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | acathrow, bazulay, dyasny, ecohen, iheim, oramraz, Rhev-m-bugs, srevivo, ykaul |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | infra network | ||
Fixed In Version: | 3.1.0.4 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-17 07:49:05 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
Elena
2012-06-21 07:52:47 UTC
entire update of network (by-name [1]) won't work cause, used following pattern [2] to retrieve network by-name while actually /api/network is non-searchable collection, bottom line, restapi reports /api/network collection as searchable while it is not. p.s future versions of CLI will not retrieve object on update before setting fields in it [3] [1] update network my_network --description aaa --name bbb [2] /api/networks?search=name%3Dmy_network [3] https://bugzilla.redhat.com/show_bug.cgi?id=834202 Oded, you have simple workaround: update network by id [1], so i'm not sure this is high priority bug. [1] [oVirt shell (connected)]# update network "e7449227-31a0-46a9-856c-e61439dade62" --description aaa --name bbb id : e7449227-31a0-46a9-856c-e61439dade62 name : bbb description : aaa data_center-id: c747d78b-ee6a-485c-8f81-1b9d46be51e9 display : False mtu : 0 required : False status-state : non_operational stp : False usages-usage : VM *** Bug 834841 has been marked as a duplicate of this bug. *** use sdk >= 3.1.0.4 Verified in rhevm-sdk-3.1.0.5-1.el6ev.noarch.rpm, rhevm-cli-3.1.0.7-1.el6ev.noarch.rpm |