Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1900126

Summary: Creating a VM results in suggestion to create a default storage class when one already exists
Product: OpenShift Container Platform Reporter: Ashley D'Andrea <jdandrea>
Component: Console Kubevirt PluginAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.7CC: aos-bugs, cnv-qe-bugs, gouyang, mschatzm, yzamir
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: x86_64   
OS: Mac OS   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:35:07 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:
Attachments:
Description Flags
VM Storage UI
none
wizard show default SC in info message
none
Message screenshot jdandrea: review+

Description Ashley D'Andrea 2020-11-20 21:48:58 UTC
Created attachment 1731491 [details]
VM Storage UI

Description of problem:

When a default storage class has been defined, creating a VM still results in a suggestion to create a default storage class.

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

2.5

How reproducible:

Always.

Steps to Reproduce:

1. Create a default storage class.
2. Create a VM.

Actual results:

Observe warning: "Some disks do not have a storage class defined. This virtual machine could experience issues. Please select a storage class or create a default one."

Expected results:

Either no warning or "The default storage class will be used" or whatever is most appropriate for this use case.

Additional info:

See attachment showing the warning at VM creation-time.

Comment 1 Yaacov Zamir 2020-12-08 11:01:51 UTC
Created attachment 1737579 [details]
wizard show default SC in info message

Comment 2 Yaacov Zamir 2020-12-08 11:03:03 UTC
Works for me on master, ( see attached image ).

Joe, is it fixed for you too ?

Comment 3 Matan Schatzman 2020-12-08 11:25:12 UTC
Created attachment 1737581 [details]
Message screenshot

While trying to reproduce this bug, it seems to me that the message is already changed, can you please confirm using master version if its an issue? 
Iv'e attached a screenshot with the current message.

Comment 4 Ashley D'Andrea 2020-12-08 15:55:08 UTC
Comment on attachment 1737581 [details]
Message screenshot

Thanks for this - lgtm. It will help make things clearer!

Comment 5 Yaacov Zamir 2020-12-08 16:01:56 UTC
marked as modified to let QE check that it's actually fixed.

Comment 7 Ashley D'Andrea 2020-12-14 14:33:00 UTC
Thank you!

Comment 8 Guohua Ouyang 2020-12-16 03:15:24 UTC
verified on 4.7.0-0.nightly-2020-12-13-202314

Comment 11 errata-xmlrpc 2021-02-24 15:35:07 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.7.0 security, bug fix, and enhancement 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-2020:5633