Bug 2263472

Summary: change the sample yaml in the CSV
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Nitin Goyal <nigoyal>
Component: odf-operatorAssignee: Nitin Goyal <nigoyal>
Status: CLOSED ERRATA QA Contact: Elad <ebenahar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.15CC: kramdoss, muagarwa, odf-bz-bot
Target Milestone: ---   
Target Release: ODF 4.15.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.15.0-138 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2263473 2263474 2263475 2263476 (view as bug list) Environment:
Last Closed: 2024-03-19 15:32:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2263473, 2263474, 2263475, 2263476    

Description Nitin Goyal 2024-02-09 06:42:59 UTC
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

Comment 2 Nitin Goyal 2024-02-09 07:39:13 UTC
efforts to verify it will be quite simple, We just need to look at the CSV yaml output

Comment 3 Nitin Goyal 2024-02-09 07:42:22 UTC
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"
          }
        }
      ]

Comment 4 krishnaram Karthick 2024-02-09 07:43:58 UTC
We have a customer issue and the verifiction is fairly simple. so adding a blocker flag and providing qa ack.

Comment 9 Elad 2024-03-03 12:16:04 UTC
Using latest 4.15 build (4.15.0-150):


apiVersion: operators.coreos.com/v1alpha1
kind: ClusterServiceVersion
metadata:
  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"
          }
        }
      ]

Comment 10 errata-xmlrpc 2024-03-19 15:32:41 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 (Important: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & 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/RHSA-2024:1383