Bug 2000628 - ibm-flashsystem-storage-storagesystem got created without any warning even when the attempt was cancelled
Summary: ibm-flashsystem-storage-storagesystem got created without any warning even wh...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 4.10.0
Assignee: Afreen
QA Contact: Jilju Joy
URL:
Whiteboard:
Depends On:
Blocks: 2022303
TreeView+ depends on / blocked
 
Reported: 2021-09-02 14:27 UTC by Jilju Joy
Modified: 2023-09-15 01:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2022303 (view as bug list)
Environment:
Last Closed: 2022-03-10 16:07:01 UTC
Target Upstream Version:
Embargoed:
prasriva: needinfo-
prasriva: needinfo-


Attachments (Terms of Use)
Screen recording (2.20 MB, video/webm)
2021-09-02 14:27 UTC, Jilju Joy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10375 0 None open Bug 2000628: Fix creation of ibm storage system at backing storage step 2021-11-02 06:07:09 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:07:30 UTC

Description Jilju Joy 2021-09-02 14:27:37 UTC
Created attachment 1820051 [details]
Screen recording

Description of problem:
Storagesystem "ibm-flashsystem-storage" got created immediately when "Next" button was clicked in the "Backing store" page. The attempt to create the storage system was actually cancelled as seen in the attached screen recording.
There is no warning given in "Backing store" page which makes the user aware of what is going to happen if "Next" button in "Backing Storage" page is clicked.

Screen recording video is attached.

Version-Release number of selected component (if applicable):
OCP 4.9.0-0.nightly-2021-09-01-193941
odf-operator.v4.9.0-123.ci

How reproducible:
Always

Steps to Reproduce:
1. When "ocs-storagecluster-storagesystem" storage system is already present, go to Operators --> Installed Operators --> Select Openshift Data Foundation
2. Go to Storage System tab and click "Create StorageSystem" button.
3. The option available in "Backing Storage" page is "Connect an external storage platform" and "Full deployment". Click "Next".
4. In the "Create Storage class" page, click "Back".
5. Click cancel button from "Backing Storage" page.
6. Verify "ibm-flashsystem-storage-storagesystem" storagesystem is not created. 


Actual results:
Storage system "ibm-flashsystem-storage-storagesystem" got created.

Expected results:
Clicking cancel button should terminate the process of creating the storagesystem and no leftover resources should be present. Instead, in this case, a new storage system got created and ibm-storage-odf-operator operator was installed even after cancelling the creation of the storage system.


Additional info:

Comment 7 Pranshu Srivastava 2021-10-07 13:26:25 UTC
@hdavid I made this change and pushed a patch (https://github.com/openshift/console/pull/10195) but as I pointed out in https://bugzilla.redhat.com/show_bug.cgi?id=2000628#c5, the deletion takes forever if we try to delete it while it's being created. I think a visual feedback of some sort before the creation occurs is the way to go here.

Looping in @afrahman as well, for any suggestions on how to move forward. Thanks.

Comment 23 errata-xmlrpc 2022-03-10 16:07:01 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

Comment 24 Red Hat Bugzilla 2023-09-15 01:14:36 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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