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

Bug 877003

Summary: RESTAPI: '[?;]current' query parameter in: POST /api/vms/xxx/cdroms/yyy value does't seem to matter
Product: Red Hat Enterprise Virtualization Manager Reporter: Barak Dagan <bdagan>
Component: ovirt-engine-restapiAssignee: Michael Pasternak <mpastern>
Status: CLOSED DUPLICATE QA Contact: Barak Dagan <bdagan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: bazulay, dyasny, ecohen, iheim, mpastern, pstehlik, Rhev-m-bugs, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-15 18:50:15 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 Barak Dagan 2012-11-15 14:09:21 UTC
Description of problem:
Same results returns using the current parameters with all possible options:
True, False and none (no parameter), seems like the true value is used always, since the return results klolooks the same, he file_id doesn't registered in the config (DB) in false value.


Version-Release number of selected component (if applicable):
Si24.1

How reproducible:
Always

Steps to Reproduce:
1. while VM is up send the following api call:
2. PUT api/vms/xxx/cdroms/yyy;current=True

<cdrom id="xxx">
    <file id="zzz.iso"/>
</cdrom>

3.PUT api/vms/xxx/cdroms/yyy;current=False

<cdrom id="xxx">
    <file id="zzz.iso"/>
</cdrom>
  
Actual results:
-- Returned XML: 

  <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  <cdrom id="yyy">
      <file id="zzziso"/>
  </cdrom>

-- no config change in any of the configurations

Expected results:
-- different behaviour for true and false parameter.

Additional info:

Comment 1 Michael Pasternak 2012-11-15 18:50:15 UTC

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