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

CNO reporting incorrect status

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.11.z
    • Networking / ovn-kubernetes
    • None
    • None
    • SDN Sprint 228, SDN Sprint 229, SDN Sprint 230
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-3114. The following is the description of the original issue:
      —
      Description of problem:

      When running a Hosted Cluster on Hypershift the cluster-networking-operator never progressed to Available despite all the components being up and running

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

      quay.io/openshift-release-dev/ocp-release:4.11.11-x86_64 for the hosted clusters
hypershift operator is quay.io/hypershift/hypershift-operator:4.11
4.11.9 management cluster

      How reproducible:

      Happened once

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

      oc get co network reports False availability

      Expected results:

      oc get co network reports True availability

      Additional info:

       

              pdiak@redhat.com Patryk Diak
              openshift-crt-jira-prow OpenShift Prow Bot
              Ross Brattain Ross Brattain
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: