Bug 1958787

Summary:	VM/VMI link changes to `kubevirt.io~v1~VirtualMachineInstance` on CNV 4.8
Product:	Container Native Virtualization (CNV)	Reporter:	Guohua Ouyang <gouyang>
Component:	Virtualization	Assignee:	sgott
Status:	CLOSED WORKSFORME	QA Contact:	Israel Pinto <ipinto>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.6.0	CC:	cnv-qe-bugs, fdeutsch, gouyang, ibezukh, ipinto, rmohr, sgott, zpeng
Target Milestone:	---	Keywords:	Reopened, TestBlocker
Target Release:	future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1907352	Environment:
Last Closed:	2021-05-18 10:08:33 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:	1907352
Bug Blocks:

Description Guohua Ouyang 2021-05-10 07:15:38 UTC

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

Description of problem:
On OCP 4.7 + CNV 2.6, the vm/vmi link in VM events is "/k8s/ns/default/kubevirt.io~v1~VirtualMachineInstance/vm-example"
On OCP 4.6 + CNV 2.5, the link of vm/vmi is "/k8s/ns/default/virtualmachineinstances/vm-example".

Some UI functionalities are broken with this change.

Version-Release number of selected component (if applicable):
CNV 2.6 

How reproducible:
100%

Steps to Reproduce:
1. Create a vm from default yaml
2. Start the VM
3. Click vmi in the events tab.

Actual results:
It redirects to "/k8s/ns/default/kubevirt.io~v1~VirtualMachineInstance/vm-example", not "/k8s/ns/default/virtualmachineinstances/vm-example".

Expected results:
It redirects to "/k8s/ns/default/virtualmachineinstances/vm-example".

Additional info:

--- Additional comment from Roman Mohr on 2020-12-14 19:32:59 CST ---

That should solve it: https://code.engineering.redhat.com/gerrit/gitweb?p=kubevirt.git;a=summary

--- Additional comment from Roman Mohr on 2020-12-14 19:33:30 CST ---

2.6 was built against latest master and not against the release branch. A fix is on the way.

--- Additional comment from zhe peng on 2021-01-04 14:53:13 CST ---

verify with build cnv2.6
$ oc version
Client Version: 4.6.0-0.nightly-2020-07-25-091217
Server Version: 4.7.0-fc.0
Kubernetes Version: v1.20.0+87544c5

Click vmi in the events tab

<a class="co-resource-item__resource-name" data-test-id="vm-fedora" href="/k8s/ns/default/virtualmachineinstances/vm-fedora">vm-fedora</a>
It redirects to right place, move to verified.

--- Additional comment from errata-xmlrpc on 2021-02-16 19:56:22 CST ---

This bug has been added to advisory RHSA-2020:59539 by Gal Ben Haim (gbenhaim)

--- Additional comment from errata-xmlrpc on 2021-03-10 08:08:59 CST ---

Bug report changed to RELEASE_PENDING status by Errata System.
Advisory RHSA-2020:59539-07 has been changed to PUSH_READY status.
https://errata.devel.redhat.com/advisory/59539

--- Additional comment from errata-xmlrpc on 2021-03-10 19:22:41 CST ---

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 (Moderate: OpenShift Virtualization 2.6.0 security and bug fix update), 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/RHSA-2021:0799

Comment 2 sgott 2021-05-14 12:24:41 UTC

Guohua, I believe the versioning on this BZ might be a mistake. From the description I suspect you meant to set the "Version" field and not the "Target Release" field. Is that a correct assumption?

I'm setting these fields to what I think is correct, but please feel free to chime in if you disagree.

Comment 3 Guohua Ouyang 2021-05-18 10:08:33 UTC

The problem is gone again on latest CNV 4.8.