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

hcp payload doesn't respect multiple mirrors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z, 4.19.z, 4.20.0
    • HyperShift
    • Important
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Fix hcp payload doesn't respect multiple mirrors
    • Bug Fix
    • In Progress

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

      Hcp payload cannot handle multiple mirrors。
According to OCP IDMS, when the current mirror image is unavailable, the system should continue searching for an available mirror image.

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

      
    4.14-4.19

      How reproducible:

      
    100%

      Steps to Reproduce:

          1. Configure imagecontentsourcepolicy in mgmt cluster with multi mirrors
spec:
  repositoryDigestMirrors:
  - mirrors:
    - virthost.ostest.test.metalkube.org:5000/fake1/local-release-image
    - virthost.ostest.test.metalkube.org:5000/fake2/local-release-image
    - virthost.ostest.test.metalkube.org:5000/localimages/local-release-image
    source: registry.build11.ci.openshift.org/ci-op-dctpdi4x/release
  - mirrors:
    - virthost.ostest.test.metalkube.org:5000/fake1/local-release-image
    - virthost.ostest.test.metalkube.org:5000/fake2/local-release-image
    - virthost.ostest.test.metalkube.org:5000/localimages/local-release-image
    source: registry.ci.openshift.org/ocp/4.18-2025-04-07-175252
    2.Create hcp in the disconnect cluster
    3.

      Actual results:
      hostedcluster report error:

        - lastTransitionTime: "2025-04-08T11:33:46Z"
      message: 'failed to get controlPlaneOperatorImageLabels: failed to look up image
        metadata for registry.ci.openshift.org/ocp/4.18-2025-04-07-175252@sha256:fdf4ccd652cfd91e18f5d58f236863b79c15ee4e088e23880eef06c8ad3b1ac7:
        failed to obtain root manifest for registry.ci.openshift.org/ocp/4.18-2025-04-07-175252@sha256:fdf4ccd652cfd91e18f5d58f236863b79c15ee4e088e23880eef06c8ad3b1ac7:
        manifest unknown: manifest unknown'
      observedGeneration: 2
      reason: ReconciliationError
      status: "False"
      type: ReconciliationSucceeded

      Expected results:

      should create the hosted cluster successfully.

      Additional info:

              rhn-support-liangli Liangquan Li
              openshift-crt-jira-prow OpenShift Prow Bot
              XiuJuan Wang XiuJuan Wang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: