Bug 1977355

Summary: [CNV] Virtualization does not show under workloads in console
Product: Container Native Virtualization (CNV) Reporter: Benjamin Schmaus <bschmaus>
Component: User ExperienceAssignee: Tal Nisan <tnisan>
Status: CLOSED WORKSFORME QA Contact: Oded Ramraz <oramraz>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.6.5CC: asimonel, cnv-qe-bugs, dhawker, fdeutsch, gouyang, stirabos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-26 07:22:24 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:

Description Benjamin Schmaus 2021-06-29 14:02:06 UTC
Description of problem:
Install a SNO node of 4.8.0-rc.0 and then install CNV 2.6.5.   The operator and pods for HCO all appear running and operator hub confirms everything succeeded.  However the Virtualization tab under Workloads in Console does not appear.  Tried with Chrome and Firefox and both showed same results


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

How reproducible:
100%

Steps to Reproduce:
1.Install 4.8.0-rc.0
2.Install CNV 2.6.5 from operator hub
3.Virtualization missing under workloads in console

Actual results:
Virtualization missing under workloads in console

Expected results:
Virtualization should be under workloads in console

Additional info:
This did work before with 4.8.0-fc.3 and CNV 2.6.5 on a SNO node

Comment 1 Guohua Ouyang 2021-06-30 02:07:09 UTC
Could you please try 4.8.0-rc.1 which includes the fixes, thanks!

Comment 2 August Simonelli 2021-06-30 06:07:40 UTC
I also hit this issue alongside Ben.
As requested I have upgraded from 4.8.0-rc.0 to 4.8.0-rc.1. 
After the upgrade I can confirm I now see the Virtualization panel under Workloads in my UI!

Comment 3 Guohua Ouyang 2021-07-12 07:25:11 UTC
Can we close this bug based on c#2 or do you want to confirm it on 4.8.0-rc.1 by yourself?

Comment 4 Guohua Ouyang 2021-07-12 07:26:21 UTC
*** Bug 1970908 has been marked as a duplicate of this bug. ***

Comment 5 Guohua Ouyang 2021-07-26 07:22:24 UTC
Close the bug for now, feel free to reopen it any questions.