Bug 1930064

Summary: Web console crashes during VM creation from template when no storage classes are defined
Product: OpenShift Container Platform Reporter: Viktor Ashirov <vashirov>
Component: Console Kubevirt PluginAssignee: Rastislav Wagner <rawagner>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: high Docs Contact:
Priority: high    
Version: 4.7CC: aos-bugs, gouyang, rawagner, yzamir
Target Milestone: ---Keywords: Reopened
Target Release: 4.8.0Flags: gouyang: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: If no storage classes are present on the cluster and user opens new VM wizard an infinite loop happens in UI Consequence: UI crashes Fix: Handle no storage class situation correctly - do not show storage class dropdown, because there is nothing to choose from. Result: UI does not crash if there are no storage classes
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-27 22:45:14 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:
Bug Depends On:    
Bug Blocks: 1930152    
Description Flags
screen recording none

Description Viktor Ashirov 2021-02-18 09:58:05 UTC
Created attachment 1757757 [details]
screen recording

Description of problem:
Web console crashes during VM creation from template when no storage classes are defined. See the attached screen recording.

$ oc get storageclass
No resources found

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

How reproducible:

Steps to Reproduce:
1. Workloads -> Virtualization -> Templates
2. Choose any template and press Create

Actual results:
Web app crashes, leaving the user with a white screen.

Expected results:
Web app should not crash.

Additional info:

Comment 2 Yaacov Zamir 2021-03-07 05:18:50 UTC
@Guohua hi, can you prioritized verifying this issue, we want to back-port the fix, but need to verify the fix first  ?

Comment 3 Guohua Ouyang 2021-03-08 06:11:40 UTC
(In reply to Yaacov Zamir from comment #2)
> @Guohua hi, can you prioritized verifying this issue, we want to back-port
> the fix, but need to verify the fix first  ?

I've looked at this already, I just don't know how to verify it with "no storage classes are defined". There are always some storage classes in the cluster which are managed by kube-controller-manager.

Comment 4 Yaacov Zamir 2021-03-08 06:56:25 UTC
closing because we can't reproduce on supported clusters

@Victor hi, the fix is merged and we can't reproduce on QE or DEV clusters, please comment here if this is still reproducible on your cluster, and what steps need to be done to create such a cluster (if bug still exist)

Comment 5 Yaacov Zamir 2021-03-08 07:02:45 UTC
moving back to ON QA,

@Guohua hi, CLOSED is not good for Github, it will not allow the fix to be backported to 4.7.z

So I moved back to ON QE, can you Verify that you can't reproduce according because there is always some storage class ?

Comment 6 Viktor Ashirov 2021-03-08 07:54:28 UTC

I'm using kcli to create a cluster. It doesn't define storage classes by default.
In 4.8.0-0.nightly-2021-03-06-055252 with kubevirt-hyperconverged-operator.v2.5.4 I no longer see the problem.

Thank you!

Comment 7 Yaacov Zamir 2021-03-08 07:56:59 UTC
moving to verified per comment#6

Comment 10 errata-xmlrpc 2021-07-27 22:45:14 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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.