Bug 1992580 - storageProfile should stay with the same value by check/uncheck the apply button
Summary: storageProfile should stay with the same value by check/uncheck the apply button
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: Aviv Turgeman
QA Contact: Leon Kladnitsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-11 11:14 UTC by Guohua Ouyang
Modified: 2022-03-10 16:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:05:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
storageProfile values (966.98 KB, application/octet-stream)
2021-08-11 11:14 UTC, Guohua Ouyang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10720 0 None Merged Bug 1992580: storageProfile should stay with the same value by check/uncheck the apply button 2021-12-30 14:28:07 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:05:28 UTC

Description Guohua Ouyang 2021-08-11 11:14:01 UTC
Created attachment 1813077 [details]
storageProfile values

Description of problem:
On storageProfile setting, check/uncheck the apply button got different values for storageClass OCS, it should stay with the same value.

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

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Guohua Ouyang 2021-08-11 11:15:29 UTC
For OCS, the optimize value is RWX/Block, uncheck the apply button, it should be RWX/Block as well.

Comment 2 Yaacov Zamir 2021-08-17 05:47:07 UTC
Expected results:

In cases a storage profile is available and the checkbutton for "apply optimization" is active.

1. the apply optimization is checked when form is first deisplayed
2. when user un-check the "apply optimization" values of access and volume modes radio buttons are set to the optimized values
3. when user check the "apply optimization" values of access and volume modes radio buttons of are set to the optimized values, and they are hidden.

In cases a storage profile is not available and the checkbutton for "apply optimization" is not active.

1. values of access and volume modes radio buttons default to rwo/filesystem, until user set other value.

Guohua, is this the correct expected results ?

Comment 3 Guohua Ouyang 2021-08-19 03:56:24 UTC
(In reply to Yaacov Zamir from comment #2)
> Expected results:
> 
> In cases a storage profile is available and the checkbutton for "apply
> optimization" is active.
> 
> 1. the apply optimization is checked when form is first deisplayed
> 2. when user un-check the "apply optimization" values of access and volume
> modes radio buttons are set to the optimized values
> 3. when user check the "apply optimization" values of access and volume
> modes radio buttons of are set to the optimized values, and they are hidden.
> 
> In cases a storage profile is not available and the checkbutton for "apply
> optimization" is not active.
> 
> 1. values of access and volume modes radio buttons default to
> rwo/filesystem, until user set other value.
> 
> Guohua, is this the correct expected results ?

Yes, exactly.

In the video, the optimized values for storageClass OCS is RWX and block, check or uncheck the "apply optimization" button should always get RWX and block.

Comment 6 Leon Kladnitsky 2022-01-02 12:13:49 UTC
Verified on master/4.10.0-0.ci-2021-12-23-133912

Comment 10 errata-xmlrpc 2022-03-10 16:05:09 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.10.3 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.

https://access.redhat.com/errata/RHSA-2022:0056


Note You need to log in before you can comment on or make changes to this bug.