Openshift Update Service pod fails with error release-manifests/release-metadata not found

Solution Unverified - Updated -

Issue

  • After installing OpenShift Update Service (OSUS), and created an update service application, the pod fails with the error 'release-manifests/release-metadata' not found:

    TRACE cincinnati::plugins::internal::graph_builder::release_scrape_dockerv2::registry] [4.Y.Z-image_name] Downloading layer sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    TRACE cincinnati::plugins::internal::graph_builder::release_scrape_dockerv2::registry] [4.Y.Z-image_name] Looking for release-manifests/release-metadata in archive sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx with xxxxxx bytes
    DEBUG cincinnati::plugins::internal::graph_builder::release_scrape_dockerv2::registry] [4.Y.Z-image_name] Could not assemble metadata from layer (sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx): 'release-manifests/release-metadata' not found
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • OpenShift Update Service (OSUS)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content