Created attachment 1583196 [details] screenshot_1 Description of problem: In the console, different components have inconsistency in naming and abbreviation. Screenshot #1 All Provided APIs have "KubeVirt" in names, but "Web User Interface" doesn't Screenshot #2 1. All instances have "full name + cluster" name, but NetworkAddonsConfig has it as "cluster" only. 2. In Types only WebUi abbreviated KubeVirt as "K", others have "KubeVirt" in type. Screenshot #3 1. KubeVirt Node Labeller Bundler, KubeVirt Template Validator and Node Maintance have matching Names and Types, but other APIs don't. Not all are on the screenshot because of the stroll bar. 2. There is "BundleR" in a name, but "Bundle" in Type for KubeVirt Node Labeller Bundler, however for KubeVirt Templates it's "Validator" always. Version-Release number of selected component (if applicable): bundle 29 Additional info:
Created attachment 1583197 [details] screenshot_2
Created attachment 1583198 [details] screenshot_3
Steve/Moran, Ryan, Nelly, are you considering this to be a blocker for 2.0? I'm not. Thus proposing to move it out.
IMO 2.1.
There were many updates to the CSV metadata - those updates have likely addressed this bug as well. Moving to ON_QA.
Created attachment 1664863 [details] screenshot 4 It looks much better than before! A couple of more details depicted on screenshot #4 from OCP 4.4 + CNV 2.3 [1]: 1: KubeVirt is spelled as Kubevirt 2: Inconsistency in Status values. All pods were in Running state when I took the screenshot 3: "Unknown" Version for all Operands is not that good UX. Is there a plan to have it at all? Should it be 2.3? Something else? Returning it back to Assign. [1] rh-osbs/container-native-virtualization-hyperconverged-cluster-operator@sha256:b449706d20bd97af7915804f493b32d6099c302ffe7a524a2d6cfab8a2658cf1 Created At 2020-02-21 09:23:25
The problem on comment 10 was specific to additional CRs that are now hidden. Now only HCO and hostpath-provisioner CRs are visible, we should re-check this.
Created attachment 1671349 [details] 2 CRs only
Indeed, there are only 2 CRs nowadays as per attachment in comment#12. I'm ok with Status inconsistency. I'm not ok with Version Unknown. Deligating it to Satyajit Bulage and his judgment =)
Hello Simone, Why 2 CR's, as I went through earlier screenshot(attached in this BZ.).? I am agree with Irina about Version Unknown, it should show the proper version. Please help me with above. Thanks, Satyajit Bulage.
Hey Simone, Ignore first question as I got answer from your comment. Thanks, Satyajit Bulage.
(In reply to Satyajit Bulage from comment #14) > Hello Simone, > > Why 2 CR's, as I went through earlier screenshot(attached in this BZ.).? > > I am agree with Irina about Version Unknown, it should show the proper > version. Fixing the version is explicitly tracked here: https://bugzilla.redhat.com/1716329 but we deferred it to 2.4 because it's blocked by https://bugzilla.redhat.com/1812151 on the management console and we cannot fix it with the current implementation on console side. Please ignore it in the verification of this bug.
As per comment 11 14 16. Verifying this BZ.
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/RHEA-2020:2011