Bug 1803132

Summary: VM Wizard always uses VirtIO for the VM rootdisk regardless what is defined in common-template
Product: OpenShift Container Platform Reporter: Radim Hrazdil <rhrazdil>
Component: Console Kubevirt PluginAssignee: Ido Rosenzwig <irosenzw>
Status: CLOSED ERRATA QA Contact: Nelly Credi <ncredi>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: aos-bugs, gouyang, irosenzw
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: VM Wizard always uses VirtIO for the VM rootdisk regardless what is defined in common-template Consequence: VM disk may use an invalid disk type Fix: Check the valid bus type using the VM's template Result: VM rootdisk is created with a valid bus type
Story Points: ---
Clone Of:
: 1810449 (view as bug list) Environment:
Last Closed: 2020-07-13 17:15:32 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:
Bug Depends On:    
Bug Blocks: 1810449    

Description Radim Hrazdil 2020-02-14 14:41:51 UTC
Description of problem:

VM Wizard seems to always use VirtIO interface for VM rootdisk instead of using interface specified in the common template

Version-Release number of selected component (if applicable):
4.4

How reproducible:
100%

Steps to Reproduce:
0. Open VM Wizard
1. Select Windows OS
2. proceed to Storage section

Actual results:
rootdisk has default interface VirtIO

Expected results:
The default interface should be selected based on common-template used, which in case of Windows VM should be sata:

disks:
  - disk:
    bus: sata
    name: rootdisk

Additional info:

Comment 3 Guohua Ouyang 2020-03-31 06:50:05 UTC
verified on 4.5.0-0.nightly-2020-03-29-224016.

Comment 5 errata-xmlrpc 2020-07-13 17:15:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409