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

Console operator goes degraded on HyperShift HCP clusters with the ingress capability disabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 4.16.0
    • Management Console
    • None
    • Important
    • None
    • Approved
    • False
    • Hide

      None

      Show
      None
    • The console operator configuration API has been enhanced with the possibility to add alternative ingress for the environments where the ingress cluster capability is disabled.
    • Bug Fix
    • In Progress

      Description of problem:

          The ingress cluster capability has been introduced in OCP 4.16 (https://github.com/openshift/enhancements/pull/1415). It includes the cluster ingress operator and all its controllers. If the ingress capability is disabled all the routes of the cluster become unavailable (no router to back them up). The console operator heavily depends on the working (admitted/active) routes to do the health checks, configure the authentication flows, client downloads, etc. The console operator goes degraded if the routes are not served by a router. The console operator needs to be able to tolerate the absence of the ingress capability.

       

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

          4.16

      How reproducible:

          Always

      Steps to Reproduce:

          1. Create ROSA HCP cluster.
          2. Scale the default ingresscontroller to 0: oc -n openshift-ingress-operator patch ingresscontroller default --type='json' -p='[{"op": "replace", "path": "/spec/replicas", "value":0}]'
          3. Check the status of console cluster operator: oc get co console
          

      Actual results:

      $ oc get co console
      NAME      VERSION  AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
      console   4.16.0   False       False         False      53s     RouteHealthAvailable: failed to GET route (https://console-openshift-console.apps.49e4812b7122bc833b72.hypershift.aws-2.ci.openshift.org): Get "https://console-openshift-console.apps.49e4812b7122bc833b72.hypershift.aws-2.ci.openshift.org": EOF

      Expected results:

      $ oc get co console
      NAME      VERSION  AVAILABLE   PROGRESSING   DEGRADED   
      console   4.16.0   True        False         False

      Additional info:

          The ingress capability cannot be disabled on a standalone OpenShift (when the payload is managed by ClusterVersionOperator). Only clusters managed HyperShift with HostedControlPlane are impacted.

            alebedev@redhat.com Andrey Lebedev
            alebedev@redhat.com Andrey Lebedev
            Melvin Joseph Melvin Joseph
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: