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

custom ingress-controller can't be deleted

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 4.12.z
    • 4.12
    • Networking / router
    • None
    • Important
    • Sprint 224, Sprint 225, Sprint 226
    • 3
    • Approved
    • False
    • Hide

      Regression in 4.12 was introduced by https://github.com/openshift/cluster-ingress-operator/pull/805 in which you can't delete ingress controllers if you set ReloadInterval specific values.

      Show
      Regression in 4.12 was introduced by https://github.com/openshift/cluster-ingress-operator/pull/805 in which you can't delete ingress controllers if you set ReloadInterval specific values.
    • Hide
      *Previously, the `ingresscontroller.spec.tuniningOptions.reloadInterval` did not support decimal points as valid for `reloadInterval`. This caused an `ingress-controller` to become invalid and unable to be deleted. With this update, `ingresscontroller.spec.tuningOptions.reloadInterval` supports decimals and users can delete ingress controllers with previously unsupported time units. (link: https://issues.redhat.com/browse/OCPBUGS-236[*OCPBUGS-236*])
      Show
      *Previously, the `ingresscontroller.spec.tuniningOptions.reloadInterval` did not support decimal points as valid for `reloadInterval`. This caused an `ingress-controller` to become invalid and unable to be deleted. With this update, `ingresscontroller.spec.tuningOptions.reloadInterval` supports decimals and users can delete ingress controllers with previously unsupported time units. (link: https://issues.redhat.com/browse/OCPBUGS-236 [* OCPBUGS-236 *])
    • Bug Fix
    • Done

    Description

      Description of problem: After I run the golang script for OCP-53608, I find the created 

      ingress-controller couldn't be deleted

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

      4.12.0-0.nightly-2022-08-15-150248

      How reproducible: Run the script and try to delete the custom ingress-controller

      Steps to Reproduce:
      1.

      % oc get clusterversion

      NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS

      version   4.12.0-0.nightly-2022-08-15-150248   True        False         43m     Cluster version is 4.12.0-0.nightly-2022-08-15-150248

      shudi@Shudis-MacBook-Pro openshift-tests-private %

      2. Run the script

      shudi@Shudis-MacBook-Pro openshift-tests-private % ./bin/extended-platform-tests run all --dry-run | grep 53608 | ./bin/extended-platform-tests run -f -

      ...

      ---------------------------------------------------------

      Received interrupt.  Running AfterSuite...

      ^C again to terminate immediately

      Aug 18 10:35:51.087: INFO: Running AfterSuite actions on all nodes

      Aug 18 10:35:51.088: INFO: Waiting up to 7m0s for all (but 100) nodes to be ready

      STEP: Destroying namespace "e2e-test-router-tunning-77627" for this suite.

      Aug 18 10:35:54.654: INFO: Running AfterSuite actions on node 1

       

      failed: (15m4s) 2022-08-18T02:35:54 "[sig-network-edge] Network_Edge should Author:shudili-Low-53608-Negative Test of Expose a Configurable Reload Interval in HAproxy [Suite:openshift/conformance/parallel]"

       

      Failing tests:

       

      [sig-network-edge] Network_Edge should Author:shudili-Low-53608-Negative Test of Expose a Configurable Reload Interval in HAproxy [Suite:openshift/conformance/parallel]

       

      error: 1 fail, 0 pass, 0 skip (15m4s)

      shudi@Shudis-MacBook-Pro openshift-tests-private % 

      3.  show the ingress-controllers

      shudi@Shudis-MacBook-Pro openshift-tests-private % oc -n openshift-ingress-operator get ingresscontroller

      NAME       AGE

      default    113m

      ocp53608   42m

      shudi@Shudis-MacBook-Pro openshift-tests-private %

       

      4. Try to delete the ingress-controller ocp53608, when the message "ingresscontroller.operator.openshift.io "ocp53608" deleted" appears, it is hanged for a long time until the error message appears.

      shudi@Shudis-MacBook-Pro openshift-tests-private % oc -n openshift-ingress-operator delete ingresscontroller ocp53608

      ingresscontroller.operator.openshift.io "ocp53608" deleted

      error: An error occurred while waiting for the object to be deleted: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeedingUnable to connect to the server: dial tcp 35.194.1.60:6443: i/o timeout

      shudi@Shudis-MacBook-Pro openshift-tests-private %

       

      5. After "ingresscontroller.operator.openshift.io "ocp53608" deleted" message appears, show the ingress-controller, ocp53608 isn't deleted

      shudi@Shudis-MacBook-Pro golang % oc -n openshift-ingress-operator get ingresscontroller

      NAME       AGE

      default    3h

      ocp53608   109m

      shudi@Shudis-MacBook-Pro golang %

       

      6.  After the error message(rror: An error occurred while waiting for the object to be deleted) appears, try to show the ingresscontroller

      shudi@Shudis-MacBook-Pro openshift-tests-private % oc -n openshift-ingress-operator get ingresscontroller

      E0818 12:21:57.272967    4168 request.go:1085] Unexpected error when reading response body: net/http: request canceled (Client.Timeout or context cancellation while reading body)

      E0818 12:21:57.273379    4168 request.go:1085] Unexpected error when reading response body: net/http: request canceled (Client.Timeout or context cancellation while reading body)

      E0818 12:21:57.274306    4168 request.go:1085] Unexpected error when reading response body: net/http: request canceled (Client.Timeout or context cancellation while reading body)

      Unable to connect to the server: dial tcp 35.194.1.60:6443: i/o timeout

      shudi@Shudis-MacBook-Pro openshift-tests-private %

       

      Actual results:  ingress-controller ocp53608  is still there after executed the oc delete command

      Expected results:

      ingress-controller ocp53608  will be deleted soon after executed the oc delete command

      Additional info:

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-2429 ReloadInterval E2E test has both incorrect verifications and a race condition

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1554 Bump cluster-ingress-operator to k8s 1.25

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          links to

          GitHub openshift/api#1275: OCPBUGS-236: Add missing time units to ingresscontroller.spec.tuningOptions.reloadInterval

          GitHub openshift/cluster-ingress-operator#830: OCPBUGS-236: Bump openshift/api for reloadInterval fix

          Activity

            People

              gspence@redhat.com Grant Spence
              shudili@redhat.com Shudi Li
              Shudi Li Shudi Li
              Joe Aldinger Joe Aldinger
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: