Bug 1656030

Summary: Kubevirt-apb shows wrong version in the UI
Product: Container Native Virtualization (CNV) Reporter: Nelly Credi <ncredi>
Component: InstallationAssignee: Ohad Levy <ohadlevy>
Status: CLOSED WONTFIX QA Contact: Irina Gulina <igulina>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.3CC: cnv-qe-bugs, rhallise
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: 2018-12-04 15:49:11 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:
Attachments:
Description Flags
screenshot none

Description Nelly Credi 2018-12-04 13:48:34 UTC
Created attachment 1511349 [details]
screenshot

Description of problem:

*This is not how we are telling customers to deploy*
but if a customer would go to the OCP service catalog and try to deploy kubevirt from there,
he will see a version dropdown list with one value - 0.9.3 

Version-Release number of selected component (if applicable):
kubevirt-apb-v3.11-14

How reproducible:
100%

Steps to Reproduce:
1. import the hidden apb
2. go to ocp console and double click the kubevirt-apb
3. see 'version' param

Actual results:
only available version is 0.9.3

Expected results:
d/s v1.3.0 version

Additional info:

Comment 1 Ryan Hallisey 2018-12-04 15:47:41 UTC
0.9.3 is used to select the offline downstream templates so we'll use to keep it.  So this is missing a downstream translation.  It's not ideal, but tag is what will reflect the version.

Comment 2 Ryan Hallisey 2018-12-04 15:48:44 UTC
downstream translation for this would be a large change based on how we're pulling in the templates now.  I think that why this was deprioritized.