Skip to content

Fix OKD release override on cross-architecture KVM - #881

Closed
pedrolzmaia wants to merge 1 commit into
karmab:mainfrom
pedrolzmaia:fix/okd-cross-arch-release-override
Closed

Fix OKD release override on cross-architecture KVM#881
pedrolzmaia wants to merge 1 commit into
karmab:mainfrom
pedrolzmaia:fix/okd-cross-arch-release-override

Conversation

@pedrolzmaia

@pedrolzmaia pedrolzmaia commented Aug 14, 2026

Copy link
Copy Markdown

Summary

Skip the cross-architecture release image override for OKD on virtualized providers while preserving the existing behavior for OCP.

Issue

Fixes #882

Problem

When an arm64 client controls a remote x86_64 KVM host, kcli appends the target architecture to the OKD SCOS release tag. This produces a nonexistent image such as quay.io/okd/scos-release:4.21.0-okd-scos.11-x86_64, causing manifest unknown during node-image-pull.

Fix

Do not set the architecture-suffixed release override for OKD. The installer then uses the valid OKD release tag without the -x86_64 suffix.

Validation

An OKD 4.21 installation using this change completed successfully through Install complete!.

@pedrolzmaia
pedrolzmaia marked this pull request as ready for review August 14, 2026 19:30
@pedrolzmaia
pedrolzmaia force-pushed the fix/okd-cross-arch-release-override branch from 987a129 to 6eb4704 Compare August 14, 2026 19:33
@karmab

karmab commented Aug 15, 2026

Copy link
Copy Markdown
Owner

sorry I missed your commit and fixed it in 392f955

@karmab karmab closed this Aug 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OKD install fails on cross-architecture KVM with nonexistent release tag

2 participants