review changes

Author: camilamacedo86

test/e2e/features/recover.feature

@@ -142,11 +142,11 @@ Feature: Recover cluster extension from errors that might occur during its lifet
     And ClusterExtension is available
     And resource "deployment/test-operator" is available
     And resource "configmap/test-configmap" is available
-    And ClusterCatalog "test" is deleted
     # Catalog deletion triggers automatic reconciliation via ClusterCatalog watch
     # Wait for reconciliation to complete by checking the status condition
-    When ClusterExtension reports Installed as True
-    Then resource "deployment/test-operator" is available
+    When ClusterCatalog "test" is deleted
+    Then ClusterExtension reports Installed as True
+    And resource "deployment/test-operator" is available
     And resource "configmap/test-configmap" is available
 
   Scenario: Resources are restored after catalog deletion
@@ -249,63 +249,14 @@ Feature: Recover cluster extension from errors that might occur during its lifet
     And ClusterExtension is rolled out
     And ClusterExtension is available
     And bundle "test-operator.1.0.0" is installed in version "1.0.0"
-    And ClusterCatalog "test" is deleted
-    When ClusterExtension is updated to change version
-      """
-      apiVersion: olm.operatorframework.io/v1
-      kind: ClusterExtension
-      metadata:
-        name: ${NAME}
-      spec:
-        namespace: ${TEST_NAMESPACE}
-        serviceAccount:
-          name: olm-sa
-        source:
-          sourceType: Catalog
-          catalog:
-            packageName: test
-            version: "1.0.1"
-            selector:
-              matchLabels:
-                "olm.operatorframework.io/metadata.name": test-catalog
-      """
+    When ClusterCatalog "test" is deleted
+    And ClusterExtension is updated to version "1.0.1"
     # Wait for reconciliation after the version change request
+    # Note: Retrying status means controller will auto-upgrade when catalog becomes available
     And ClusterExtension reports Progressing as True with Reason Retrying
     # Verify upgrade did not proceed: version remains at 1.0.0 (not 1.0.1)
     Then bundle "test-operator.1.0.0" is installed in version "1.0.0"
     And ClusterExtension reports Installed as True
-    # Note: Retrying status means controller will auto-upgrade when catalog becomes available
-
-  @BoxcutterRuntime
-  Scenario: Extension with revisions continues running after catalog deletion
-    Given ServiceAccount "olm-sa" with needed permissions is available in ${TEST_NAMESPACE}
-    And ClusterExtension is applied
-      """
-      apiVersion: olm.operatorframework.io/v1
-      kind: ClusterExtension
-      metadata:
-        name: ${NAME}
-      spec:
-        namespace: ${TEST_NAMESPACE}
-        serviceAccount:
-          name: olm-sa
-        source:
-          sourceType: Catalog
-          catalog:
-            packageName: test
-            selector:
-              matchLabels:
-                "olm.operatorframework.io/metadata.name": test-catalog
-      """
-    And ClusterExtension is rolled out
-    And ClusterExtension is available
-    And ClusterExtensionRevision "${NAME}-1" reports Available as True with Reason ProbesSucceeded
-    And resource "deployment/test-operator" is available
-    And ClusterCatalog "test" is deleted
-    # Wait for reconciliation to complete after catalog deletion
-    When ClusterExtension reports Installed as True
-    Then resource "deployment/test-operator" is available
-    And ClusterExtensionRevision "${NAME}-1" reports Available as True with Reason ProbesSucceeded
 
   @BoxcutterRuntime
   Scenario: Revision remains available after catalog deletion