Bug 1807600

Summary:	templates are prefilled incorrectly in flavor modal
Product:	OpenShift Container Platform	Reporter:	Filip Krepinsky <fkrepins>
Component:	Console Kubevirt Plugin	Assignee:	Filip Krepinsky <fkrepins>
Status:	CLOSED ERRATA	QA Contact:	Nelly Credi <ncredi>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3.0	CC:	aos-bugs, gouyang, ncredi
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: wrong templates were chosen in VM flavor modal Consequence: wrong CPU/Memory values and labels were set to the VM Fix and Result: It is not possible to expect that templates will be compatible. So currently it is possible to switch only between the underlying template and CUSTOM mem/cpu and the underlying template is never changed.	Story Points:	---
Clone Of:	1804254	Environment:
Last Closed:	2020-05-13 21:59:58 UTC	Type:	---
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:	1804254
Bug Blocks:

Description Filip Krepinsky 2020-02-26 17:21:35 UTC

+++ This bug was initially created as a clone of Bug #1804254 +++

Description of problem:
Wrong values are loaded from base template.

How reproducible:
100


Steps to Reproduce:
1. Create a fedora template with Custom flavor (1 cpu,1 GiB RAM) with the Wizard
2. change the flavor in flavor modal to small/large etc.
3. the cpu and memory is copied from wrong templates (e.g. windows and centos)
4. The template is labeled and annotated inccorectly (base template pointers, vmi labels)


Actual results:


Expected results:
All correct values are preffiled and changed accordingly 


Additional info:
User templates are not taken into account when changing the flavor of VM - e.g. validations

--- Additional comment from Filip Krepinsky on 2020-02-26 14:10:21 UTC ---

The definition of the bug has changed as the requirements changed. There should not be any changing of the underlying template in flavor modal, so we should revert this feature and allow only:

- flavor from the user/one base template
- custom flavor

Comment 3 Guohua Ouyang 2020-03-12 03:04:03 UTC

verified on 4.4.0-0.nightly-2020-03-06-170328.

Comment 5 errata-xmlrpc 2020-05-13 21:59:58 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:0581