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

Some platforms are missing scope change instructions in the Progressing status

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.18.0
    • 4.13, 4.12, 4.14, 4.15, 4.16, 4.17
    • Networking / router
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 2
    • Moderate
    • None
    • None
    • Rejected
    • NE Sprint 258, NE Sprint 259
    • 2
    • Done
    • Bug Fix
    • Hide
      * Previously, instructions that guided the user after changing the `LoadBalancer` parameter from `External` to `Internal` were missing for PowerVS, Alibaba, and OpenStack platform. This caused the Ingress Controller to be put in a permanent `Progressing` state. With this release the message `The IngressController scope was changed from Internal to External" is followed by `To effectuate this change, you must delete the service` resolving the permanent `Progressing` state. (link:https://issues.redhat.com/browse/OCPBUGS-39151[*OCPBUGS-39151*])
      Show
      * Previously, instructions that guided the user after changing the `LoadBalancer` parameter from `External` to `Internal` were missing for PowerVS, Alibaba, and OpenStack platform. This caused the Ingress Controller to be put in a permanent `Progressing` state. With this release the message `The IngressController scope was changed from Internal to External" is followed by `To effectuate this change, you must delete the service` resolving the permanent `Progressing` state. (link: https://issues.redhat.com/browse/OCPBUGS-39151 [* OCPBUGS-39151 *])
    • None
    • None
    • None
    • None

      Description of problem:

      When you update the IngressController's Scope on PowerVS, Alibaba Cloud, or OpenStack, a Progressing status condition is added that only says:
      
      "The IngressController scope was changed from "Internal" to "External"
      
      It's missing the instructions we see on AWS which begin with "To effectuate this change, you must delete the service..."
      
      These platforms do NOT have mutable scope (meaning you must delete the service to effectuate), so the instructions should be included.

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

          4.12+

      How reproducible:

          100%

      Steps to Reproduce:

          1. On PowerVS, Alibaba Cloud, or OpenStack, create an IngressController
          2. Now change the scope of ingresscontroller.spec.endpointPublishingStrategy.loadBalancer.scope   

      Actual results:

          Missing "To effectuate this change, you must delete the service..." instructions

      Expected results:

          Should contain "To effectuate this change, you must delete the service..." instructions

      Additional info:

          

              gspence@redhat.com Grant Spence (Inactive)
              gspence@redhat.com Grant Spence (Inactive)
              None
              None
              Hongan Li Hongan Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: