Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-56177

[AWS] destroyer will go into an infinite loop in mx-central-1 region (4.18)

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Critical
    • None
    • Proposed
    • None
    • Done
    • Bug Fix
    • Hide
      Before this update, destroying a cluster in the unsupported region `mx-central-1` caused the destroyer to fail to find a partition and not exit. As a consequence, you could not destroy a Red Hat OpenShift Container Platform cluster in the `mx-central-1`region due to constant error reporting. With this release, the destroyer does not report errors for the unsupported region `mx-central-1`, which enables the successful destruction of a cluster. (link:https://issues.redhat.com/browse/OCPBUGS-56177[OCPBUGS-56177])
      Show
      Before this update, destroying a cluster in the unsupported region `mx-central-1` caused the destroyer to fail to find a partition and not exit. As a consequence, you could not destroy a Red Hat OpenShift Container Platform cluster in the `mx-central-1`region due to constant error reporting. With this release, the destroyer does not report errors for the unsupported region `mx-central-1`, which enables the successful destruction of a cluster. (link: https://issues.redhat.com/browse/OCPBUGS-56177 [ OCPBUGS-56177 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-56020. The following is the description of the original issue:
      —
      Description of problem:

      mx-central-1 is not supported at this moment (https://issues.redhat.com/browse/OCPSTRAT-1890), but if a user tries to install OCP in this region and destroy it, the destroyer will constantly report the following error and won't exit.
time="2025-03-14T10:34:47+08:00" level=info msg="error while finding EC2 instances to delete" error="no partition found for region \"mx-central-1\""

      Version-Release number of selected component (if applicable):

      4.18.1

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create cluster in mx-central-1
2. Destroy cluster

      Actual results:

      As described

      Expected results:

      Destroyer could exit within a reasonable time.

      Additional info:

              rh-ee-bbarbach Brent Barbachem
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Weinan Li Weinan Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: