Bug 1995467 - Storagesystem "ibm-flashsystem-storage" got created without clicking on Create button
Summary: Storagesystem "ibm-flashsystem-storage" got created without clicking on Creat...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.0
Assignee: Afreen
QA Contact: Jilju Joy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-19 08:31 UTC by Jilju Joy
Modified: 2021-11-22 21:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-22 21:47:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screencast (6.53 MB, video/webm)
2021-08-19 08:31 UTC, Jilju Joy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4712 0 None None None 2021-11-22 21:47:12 UTC

Description Jilju Joy 2021-08-19 08:31:18 UTC
Created attachment 1815530 [details]
Screencast

Description of problem:
Storagesystem "ibm-flashsystem-storage" got created when "Cancel" button was clicked in the "Review and Create" page.

"odf-storage-system"(Full Deployment) storage system was in "Progressing" state when the above step is performed.

Screen cast is attached. Jump to 1:31 to see the flow.

$ oc get operator 
NAME                                         AGE
ibm-storage-odf-operator.openshift-storage   26m
ocs-operator.openshift-storage               35m
odf-operator.openshift-storage               36m

$ oc get storagesystem
NAME                      STORAGE-SYSTEM-KIND                       STORAGE-SYSTEM-NAME       PHASE
ibm-flashsystem-storage   flashsystemcluster.odf.ibm.com/v1alpha1   ibm-flashsystem-storage   Progressing
odf-storage-system        storagecluster.ocs.openshift.io/v1        odf-storage-system        Progressing

$ oc get storagecluster
NAME                 AGE   PHASE   EXTERNAL   CREATED AT             VERSION
odf-storage-system   28m   Ready              2021-08-19T07:41:51Z   4.9.0


Version-Release number of selected component (if applicable):
OCP 4.9.0-0.nightly-2021-08-18-144658
odf-operator.v4.9.0-101.ci


How reproducible:
Reporting first occurrence

Steps to Reproduce:
1. When "odf-storage-system" storage system is already in Progressing state, go to Operators --> Installed Operators --> Select Openshift Data Foundation
2. Go to Storage System tab and click "Create StorageSystem" button.
3. Select the option "Connect an external storage platform" and select "IBM FlashSystem Storage" 
4. Select MultiCloud Object Gateway deployment type and click Next.
5. Click cancel button from "Review and Create" page.
6. Verify ibm-flashsystem-storage storagesystem is not created. 


Actual results:
ibm-flashsystem-storage storagesystem created and status is Progressing

Expected results:
ibm-flashsystem-storage storage system should not get created because the creation was cancelled from "Review and Create" page

Additional info:

Comment 9 Jilju Joy 2021-09-04 14:10:46 UTC
The issue is not reproducible with by following the procedure in #comment0. So moving this bug to Verified.

Tested in version:
4.9.0-0.nightly-2021-09-01-193941
odf-operator.v4.9.0-123.ci

As mentioned in #comment4, 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. 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.
Opened a new bug 2000628

Comment 12 errata-xmlrpc 2021-11-22 21:47:05 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 (OpenShift Container Platform 4.9.8 bug fix 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/RHBA-2021:4712


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