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

PowerVS: Fix destroy persistent TG

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.18.0
    • 4.18
    • Installer / PowerVS
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • None
    • Proposed
    • Bug Fix
    • Hide
      * Previously, when you destroyed a cluster in {ibm-power-server-title}, the Transit Gateway connections were cleaned up. With this release, if the `tgName` is set, {rh-openstack-first} will not clean up the Transit Gateway connection when you destroy a cluster. (link:https://issues.redhat.com/browse/OCPBUGS-44162[*OCPBUGS-44162*])
      Show
      * Previously, when you destroyed a cluster in {ibm-power-server-title}, the Transit Gateway connections were cleaned up. With this release, if the `tgName` is set, {rh-openstack-first} will not clean up the Transit Gateway connection when you destroy a cluster. (link: https://issues.redhat.com/browse/OCPBUGS-44162 [* OCPBUGS-44162 *])
    • None
    • None
    • None
    • None

      Description of problem:

      We were told that adding connections to a Transit Gateway also costs an exorbitant amount of money. So the create option tgName now means that we will not clean up the connections during destroy cluster.

              mturek.coreos Michael Turek
              hamzy_redhat Mark Hamzy
              None
              None
              Julie Mathew Julie Mathew (Inactive)
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: