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

Component readiness sometimes fails on 4.17->4.18 upgrades due to missing required-scc

XMLWordPrintable

    • Important
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          Sometimes the component readiness dashboard reports red for MCO, due to a missing required-scc annotation on crio-proxy. This is properly defined in 4.18, but 4.17 doesn't have it, and presumably rarely on upgrades the check for this runs before the 4.18 definition is deployed.
      
      To reduce noise we should probably also have the label in 4.17.
      
      Also see: https://issues.redhat.com/browse/OCPBUGS-46583?focusedId=26443563&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26443563

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

          4.18

      How reproducible:

          Very intermittent

      Steps to Reproduce:

          1. See CI dashboard e.g. https://sippy.dptools.openshift.org/sippy-ng/component_readiness/main?view=4.18-main     2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

              jerzhang@redhat.com Yu Qi Zhang
              jerzhang@redhat.com Yu Qi Zhang
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: