Description of problem: When OpenShift release image is mirrored to filesystem it produces a configuration manifest containing the release image signature. The filename extension is .yaml while the content is in json format. The extension should be in .json Version-Release number of selected component (if applicable): 4.9.25 How reproducible: 100% Steps to Reproduce: 1. Mirror an OpenShift release image to a filesystem oc adm release mirror -a {{ pull_secret }} --to-dir={{ workdir }}/ocp4-release quay.io/openshift-release-dev/ocp-release:{{ ocp_release_tag }} 2. A file config/signature-sha256-2eafde815e543b92.yaml is generated which has extension as .yaml while the contents are in json format. Actual results: The filename config/signature-sha256-2eafde815e543b92.yaml is having extension as .yaml Expected results: The filename config/signature-sha256-2eafde815e543b92.yaml should have .json extension Additional info:
Hello All, I'm following up on this BZ as it relates to the SFDC case : 03212723 and customer expects an update. can you please share your thoughts/findings regarding filename extension ? Thank you, have a great day Hala Elwazery Technical Account Manager - Openshift
@pkhilare @helwazer -----> Please Create a Clone BZ to get the OCP 4.11 Fix Backported to OCP 4.10 Colum Gaynor - Senior Partner Success Manager, Nokia Global Account
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069