Hide Forgot
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:
@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.
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