Bug 1806986

Summary:	Virtual machine details show Common template details
Product:	OpenShift Container Platform	Reporter:	Yaacov Zamir <yzamir>
Component:	Console Kubevirt Plugin	Assignee:	Tomas Jelinek <tjelinek>
Status:	CLOSED ERRATA	QA Contact:	Nelly Credi <ncredi>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.3.0	CC:	aos-bugs, mcarleto, ncredi, rhrazdil, yzamir
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	very small visual change, no need to document it	Story Points:	---
Clone Of:	1798644	Environment:
Last Closed:	2020-05-04 11:42:22 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:	1798644
Bug Blocks:

Description Yaacov Zamir 2020-02-25 12:07:10 UTC

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

Description of problem:

When a VM is created without using a template the common template used to create the VM is showing up under "Template" in the VM Details. This should only show the name of the VM that was used to create the VM from, otherwise it should state "no template used"
Version-Release number of selected component (if applicable):


How reproducible:
very

Steps to Reproduce:
1. Create custom Virtual Machine
2. View VM details, see under Template
3.

Actual results:

Common template link is available
Expected results:
only the link to the Virtual Machine template should be linked here, otherwise no template should be shown if the VM is custom.

Additional info:

--- Additional comment from Tomas Jelinek on 2020-02-07 11:39:12 UTC ---

this is somewhere on a border of bug and rfe. Lets call it bug but setting priority to low to not to track it as an openshift blocker

Comment 3 Radim Hrazdil 2020-02-27 15:52:24 UTC

Verified

Comment 5 errata-xmlrpc 2020-05-04 11:42:22 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