Description of problem: "Soundcard Enabled" can only be set in the UI but it's not accessible via API. Version-Release number of selected component (if applicable): is19: rhevm-restapi-3.3.0-0.26.master.el6ev.noarch rhevm-backend-3.3.0-0.26.master.el6ev.noarc How reproducible: always Steps to Reproduce: 1. perform HTTP GET https://rhevm.example.org/api/vms/VM_UUID 2. 3. Actual results: "soundcard enabled" equivalent is not available Expected results: "soundcard enabled" equivalent is displayed and can be modified via HTTP PUT Additional info:
Michal, looks like this won't make 3.4, can you retarget it?
fixed in vt3, moving to on_qa. if you believe this bug isn't released in vt3, please report to rhev-integ
rhevm-3.5.0-0.11.beta.el6ev.noarch (vt3). Confirming that VM/pool VM and template entities have now attribute 'soundcard_enabled'. However it's visible in the response only with use of HTTP header 'All-Content=true'. But... @Eldan: Is it really desired to have this general VM/template attribute hidden behind the All-Content header? Other similar attributes, like vm.delete_protected or vm.display.smartcard_enabled, are exposed without it.
Yes, we talked about it with our REST guy, the soundcard field requires an additional query to the backend\db because it's a device and not an integral part of the VM object like most VM REST fields. Because queries may affect performance the fields which require them are currently added under the 'All-Content' header (fields such as RNG and virtioSCSI).
(In reply to Eldan Shachar from comment #6) > Yes, we talked about it with our REST guy, the soundcard field requires an > additional query to the backend\db because it's a device and not an integral > part of the VM object like most VM REST fields. > > Because queries may affect performance the fields which require them are > currently added under the 'All-Content' header (fields such as RNG and > virtioSCSI). I understand, moving to VERIFIED then, rhevm-3.5.0-0.11.beta.el6ev.noarch (vt3).
RHEV-M 3.5.0 has been released