Bug 1422418

Summary: creating template does not save value in VirtIO-SCSI Enabled
Product: [oVirt] ovirt-engine Reporter: Lucie Leistnerova <lleistne>
Component: Frontend.CoreAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.1CC: bugs, tjelinek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-17 07:55:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lucie Leistnerova 2017-02-15 10:00:28 UTC
Description of problem:
When creating template from VM that has checked 'VirtIO-SCSI Enabled' it is not saved in the new template. 
Vm from this template with VirtIO-SCSI disk can't be edited until this checkbox is checked again. Error: Cannot disable VirtIO-SCSI when disks with a VirtIO-SCSI interface are plugged into the VM.

Version-Release number of selected component (if applicable):
ovirt-engine-4.1.1-0.1.el7.noarch

How reproducible: always


Steps to Reproduce:
1. create VM with VirtIO-SCSI disk, in Resource Allocation 'VirtIO-SCSI Enabled' is checked as default
2. create template from this VM
3. create new VM from this template
4. edit the VM, change nothing and click 'OK'

Actual results: template has not checked 'VirtIO-SCSI Enabled' and can't edit VM from this template


Expected results: template has checked 'VirtIO-SCSI Enabled' and the new VM also


Additional info:
Doing it in user and admin portal. 
Creating template via REST API saves the value correctly.

    <virtio_scsi>
        <enabled>true</enabled>
    </virtio_scsi>

Comment 1 Tomas Jelinek 2017-02-17 07:55:20 UTC
this is a subset of the https://bugzilla.redhat.com/show_bug.cgi?id=1422374
Closing as duplicate.

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