Bug 1950978 - the ingressclass cannot be removed even after deleting the related custom ingresscontroller
Summary: the ingressclass cannot be removed even after deleting the related custom ing...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.8.0
Assignee: Miciah Dashiel Butler Masters
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-19 10:19 UTC by Hongan Li
Modified: 2022-08-04 22:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 23:01:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-ingress-operator pull 605 0 None open Bug 1950978: ingressclass: Skip if ingresscontroller not found 2021-04-20 14:36:10 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:02:07 UTC

Description Hongan Li 2021-04-19 10:19:45 UTC 
Description of problem:
the ingressclass cannot be removed even after deleting the related ingresscontroller

Version-Release number of selected component (if applicable):
4.8.0-0.nightly-2021-04-18-101412

How reproducible:
100%

Steps to Reproduce:
1. create a custom ingresscontroller
2. check the ingressclass
3. delete the custom ingresscontroller

Actual results:
1. the ingressclass created by the custom ingresscontroller is not removed
2. delete the ingressclass manually, but it is recreated automatically.

see below steps:
$ oc -n openshift-ingress-operator delete ingresscontroller/lb-ext
ingresscontroller.operator.openshift.io "lb-ext" deleted

$ oc get ingressclass
NAME                CONTROLLER                      PARAMETERS                                        AGE
openshift-default   openshift.io/ingress-to-route   IngressController.operator.openshift.io/default   8m59s
openshift-lb-ext    openshift.io/ingress-to-route   IngressController.operator.openshift.io/lb-ext    63m

$ oc delete ingressclass openshift-lb-ext
ingressclass.networking.k8s.io "openshift-lb-ext" deleted

$ oc get ingressclass
NAME                CONTROLLER                      PARAMETERS                                        AGE
openshift-default   openshift.io/ingress-to-route   IngressController.operator.openshift.io/default   15m
openshift-lb-ext    openshift.io/ingress-to-route   IngressController.operator.openshift.io/lb-ext    3s


Expected results:
the ingressclass should be removed after deleting the ingresscontroller

Additional info:
Comment 2 Hongan Li 2021-04-25 03:10:56 UTC 
verified with 4.8.0-0.nightly-2021-04-24-175929 and passed.

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.nightly-2021-04-24-175929   True        False         70m     Cluster version is 4.8.0-0.nightly-2021-04-24-175929


$ oc get ingressclass
NAME                CONTROLLER                      PARAMETERS                                        AGE
openshift-default   openshift.io/ingress-to-route   IngressController.operator.openshift.io/default   76m
openshift-lb-int    openshift.io/ingress-to-route   IngressController.operator.openshift.io/lb-int    3s

$ oc -n openshift-ingress-operator delete ingresscontroller/lb-int
ingresscontroller.operator.openshift.io "lb-int" deleted

$ oc get ingressclass
NAME                CONTROLLER                      PARAMETERS                                        AGE
openshift-default   openshift.io/ingress-to-route   IngressController.operator.openshift.io/default   77m
Comment 5 errata-xmlrpc 2021-07-27 23:01:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2438
Note You need to log in before you can comment on or make changes to this bug.