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

CCO reads the wrong record of infrastructure sometimes

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.17.z, 4.18.z, 4.19.z, 4.20.z, 4.22.0, 4.21.z
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      This is a follow up for OCPBUGS-74384.
      In OCPBUGS-74384 issue, another infrastructure record(named cloud-provider-config) is inserted in the cluster without status part, which caused CCO pod crash due to no null pointer checking on status.
      OCPBUGS-74384 fixed the issue of null pointer checking on status.
      This BUG is to ensure CCO to read the correct record of infrastructure. In the case it should be "cluster" instead of "cloud-provider-config".       

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

      All releases    

      How reproducible:

      always    

      Steps to Reproduce:

          1.Create a ocp cluster
          2. Duplicate another infrastructure record with 1) change name from "cluster" to another like "cloud-provider-config" 2)Remove the whole status part
          3.Watch CCO pods, it will crash and restart in mins
          

      Actual results:

      CCO pod crash   

      Expected results:

      No pod crash    

      Additional info:

          

              jstuever@redhat.com Jeremiah Stuever
              jshu@redhat.com Jianping Shu
              None
              None
              Jianping Shu Jianping Shu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: