Bug 1782119

Summary: VM created from VM Template disk does not fill the disk page
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Console Kubevirt PluginAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED ERRATA QA Contact: Nelly Credi <ncredi>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3.0CC: aos-bugs, fkrepins, gouyang
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1782434 (view as bug list) Environment:
Last Closed: 2020-01-23 11:18:54 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: 1782434    
Bug Blocks:    
Attachments:
Description Flags
template yaml none

Description Guohua Ouyang 2019-12-11 08:28:22 UTC 
Description of problem:
Create a template by using disk as the provision source and use it in VM wizard, the disk page is not filled at the template does, it still need to add disk manually.

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-04-054458

How reproducible:
100%

Steps to Reproduce:
1. Create a template by using disk as the provision source
2. Create a VM by using the template
3. Click "Review and create" on the first page

Actual results:
It fails because no bootable disk is found.

Expected results:
The vm is created.

Additional info:
Comment 1 Guohua Ouyang 2019-12-11 08:29:44 UTC 
Created attachment 1643819 [details]
template yaml
Comment 2 Filip Krepinsky 2019-12-11 16:33:53 UTC 
*** Bug 1782443 has been marked as a duplicate of this bug. ***
Comment 3 Tomas Jelinek 2019-12-12 08:11:36 UTC 
*** Bug 1782439 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2020-01-23 11:18:54 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:0062