+++ This bug was initially created as a clone of Bug #2263472 +++ Description of problem (please be as detailed as possible and provide log snippets): In certain instances, customers unintentionally create two storage systems to the same storagecluster. This becomes problematic when attempting to delete one storagesystem, as it triggers the deletion of the associated storagecluster. By changing the name and reference, we aim to prevent this issue from occurring. Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=2254343 https://bugzilla.redhat.com/show_bug.cgi?id=2263441
efforts to verify it will be quite simple, We just need to look at the CSV yaml output
We need to look for the below annotation in the csv annotations: alm-examples: |- [ { "apiVersion": "odf.openshift.io/v1alpha1", "kind": "StorageSystem", "metadata": { "name": "my-flashsystemcluster-storagesystem", "namespace": "openshift-storage" }, "spec": { "kind": "flashsystemcluster.odf.ibm.com/v1alpha1", "name": "my-flashsystemcluster", "namespace": "openshift-storage" } }, { "apiVersion": "odf.openshift.io/v1alpha1", "kind": "StorageSystem", "metadata": { "name": "my-storagecluster-storagesystem", "namespace": "openshift-storage" }, "spec": { "kind": "storagecluster.ocs.openshift.io/v1", "name": "my-storagecluster", "namespace": "openshift-storage" } } ]
Please backport the fix to ODF-4.13 and update the RDT flag/text appropriately.