-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.6.z, rhel-9.8
-
None
-
Smooth transition staging to released image builds
-
None
-
image-builder
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Description
Working with rre-release bootc images requires usage of BIB and RHEL images from registry.stage.redhat.io (e.g. registry.stage.redhat.io/rhel9-eus/rhel-9.6-bootc-image-builder:9.6 and registry.stage.redhat.io/rhel9-eus/rhel-9.6-bootc:9.6).
When a RHEL OS is flagged as a release candidate, BIB ISO image generation stops working because it tries to access production repositories that are not open to the public usage yet.
rhel96-bootc: bff4a94947709dba3480eaa305b66ae6b5324156bcbb510b157047400205dd51 rhel96-bootc: Trying to pull registry.stage.redhat.io/rhel9-eus/rhel-9.6-bootc:9.6... rhel96-bootc: Getting image source signatures rhel96-bootc: Copying blob sha256:c5f0dd5b1152204d023c33dc6b62c0c435cf906d765c166d23c7885d23851776 ... ... rhel96-bootc: Generating manifest manifest-anaconda-iso.json rhel96-bootc: Errors during downloading metadata for repository 'rhel-9-for-x86_64-baseos-rpms': rhel96-bootc: - Status code: 403 for https://cdn.redhat.com/content/dist/rhel9/9.6/x86_64/baseos/os/repodata/repomd.xml (IP: 95.101.160.251) rhel96-bootc: RepoError: There was a problem reading a repository: Failed to download metadata for repo 'rhel-9-for-x86_64-baseos-rpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
We need to define a procedure for migrating between the staging and production registries without creating a disruption in the process.
What SSTs and Layered Product teams should review this?
RHEL, Bootc and Bootc Image Builder
