Bug 1776064

Summary: The default template cannot be used in vm wizard
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Console Kubevirt PluginAssignee: Ido Rosenzwig <irosenzw>
Status: CLOSED DUPLICATE QA Contact: Nelly Credi <ncredi>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3.0CC: aos-bugs, fkrepins, irosenzw, tjelinek
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1778855 1793962 (view as bug list) Environment:
Last Closed: 2020-02-26 11:22:25 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: 1793962    

Description Guohua Ouyang 2019-11-25 03:01:17 UTC 
Description of problem:
Create a default template via "VM Templates -> "Create from yaml", and try to use it in vm wizard. It says "Could not select Provision Source. No bootable device found.". On the template's network and disk tab, the nic and rootdisk are missing.

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-11-21-122827

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
The template create from "Create from yaml" can be used in vm wizard.

Additional info:
Comment 1 Tomas Jelinek 2019-12-05 14:35:22 UTC 
lowering the priority since it is not a blocker for the whole openshift, even though we will get it in 4.3 on time. It just will not be considered a blocker.
Comment 2 Tomas Jelinek 2020-01-22 11:24:13 UTC 
we agreed some time ago that this should go to z-stream. Now I can move it there, so targeting and cloning.
Comment 3 Tomas Jelinek 2020-02-05 11:47:50 UTC 
*** Bug 1778855 has been marked as a duplicate of this bug. ***
Comment 4 Filip Krepinsky 2020-02-26 11:22:25 UTC 

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