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

OS Validation check doesn't always work

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • None
    • None
    • None
    • MCO Sprint 271
    • 1
    • Done
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-55770. The following is the description of the original issue:
      —
      The checkOS validation check in the MCO uses skopeo to inspect the image in a remote registry to get the ostree.commit label and compare it with the image rolled out on disk.

      However, this doesn't always work and while it is supposed to be non-fatal it can cause issues. Here are some logs we see:

      W0428 01:57:17.195328    2541 daemon.go:2738] Unable to check manifest for matching hash: error parsing image name "docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:76a0def291cd6c38d5a0925c6000fae4347e0cdd8ba5fe1d2c2d78cc7ee97b04": invalid image name "docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:76a0def291cd6c38d5a0925c6000fae4347e0cdd8ba5fe1d2c2d78cc7ee97b04", unknown transport "docker"

              umohnani Urvashi Mohnani
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              Urvashi Mohnani
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: