Bug 840234 - REST API: response body for hotPlug nic actions is empty
Summary: REST API: response body for hotPlug nic actions is empty
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-restapi
Version: 3.1.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Mike Kolesnik
QA Contact: Yaniv Kaul
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-14 16:10 UTC by Avi Tal
Modified: 2016-04-22 04:59 UTC (History)
11 users (show)

Fixed In Version: si13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:00:45 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Avi Tal 2012-07-14 16:10:50 UTC 
Description of problem:
Response body for hotPlug nic actions is empty.
part of rest api flow is to validate the response code and response body for every action which in this case can't be done.

Steps to Reproduce:
1. add nic to VM
2. POST /api/vms/id/nics/id/<activate/deactivate>
   <action>
    <async>false</async>
    <grace_period>
        <expiry>10</expiry>
    </grace_period>
   </action>
3. response code should be 200
  
Actual results:
response code 200 but body is empty 


Expected results:
should contain the vm nic object after action is done
Comment 1 Mike Kolesnik 2012-08-01 12:01:55 UTC 
http://gerrit.ovirt.org/#/c/6813/
Comment 2 Mike Kolesnik 2012-08-01 12:03:00 UTC 
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=1dbcd75d5f344dddad591561ae74d3c479a2ea49
Comment 3 Avi Tal 2012-08-05 09:13:28 UTC 
Verify on si13 - PASS
POST (to both deactivate and activate) 
<action>
    <async>false</async>
    <grace_period>
        <expiry>10</expiry>
    </grace_period>
</action>


Response body:

<action>
    <async>false</async>
    <grace_period>
        <expiry>10</expiry>
    </grace_period>
    <status>
        <state>complete</state>
    </status>
</action>
Note You need to log in before you can comment on or make changes to this bug.