Description of problem: Unable to update VIRTIO_SCSI flag via rest api Version-Release number of selected component (if applicable): rhevm-3.6.2.5-0.1.el6.noarch How reproducible: always Steps to Reproduce: 1. Create a template with resource allocation:virtio_scsi is disabled (False) 2. update via rest PUT https://<engine-url>/api/templates/<template-id> HEADER: Content-Type: application/xml <template> <virtio_scsi enabled="true"/> </template> Actual results: response body: <virtio_scsi enabled="false"/> Expected results: <virtio_scsi enabled="true"/> Additional info: In short in rest api doesn't update the virtio_scci flag. Note that in the UI it is update it successfully.
This happens with templates and also with instance types. The proposed patch fixes the issue, and it has been verified it in the master and 3.6 branches. Allon, can you assign the bug to someone in your team, so that she/he follows the bug to completion? Backporting to the 3.6 branch should be easy, just a cherry-pick, and I already verified it works.
(In reply to Juan Hernández from comment #1) > This happens with templates and also with instance types. The proposed patch > fixes the issue, and it has been verified it in the master and 3.6 branches. > > Allon, can you assign the bug to someone in your team, so that she/he > follows the bug to completion? Backporting to the 3.6 branch should be easy, > just a cherry-pick, and I already verified it works. Thanks Juan! Daniel - please take this one over.
(In reply to Allon Mureinik from comment #2) > (In reply to Juan Hernández from comment #1) > > This happens with templates and also with instance types. The proposed patch > > fixes the issue, and it has been verified it in the master and 3.6 branches. > > > > Allon, can you assign the bug to someone in your team, so that she/he > > follows the bug to completion? Backporting to the 3.6 branch should be easy, > > just a cherry-pick, and I already verified it works. > Thanks Juan! > Daniel - please take this one over. Not sure how relevant for 3.6 since disks can't be added to an existing template any way. I.e. it could be needed only when creating a VM from a template, but then, can be changed from the new VM dialog.
Tareq, Nelly, how important is this for automation? Needs to be fixed in 3.6.z?
(In reply to Juan Hernández from comment #4) > Tareq, Nelly, how important is this for automation? Needs to be fixed in > 3.6.z? It's a trivial fix - let's just do it.
Yes it will be very nice to have
Verified on rhevm-3.6.2.6-0.1.el6.noarch