Description
An OKD installation fails during bootstrap when kcli runs on an arm64 client connected to a remote x86_64 KVM host.
Root cause
kcli detects that the client and KVM host architectures differ and sets OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE using the target architecture. The same tag construction is currently used for OCP and OKD, but OKD SCOS release tags do not have an architecture suffix.
For OKD 4.21, kcli changes the valid release image:
quay.io/okd/scos-release:4.21.0-okd-scos.11
into the nonexistent image:
quay.io/okd/scos-release:4.21.0-okd-scos.11-x86_64
The bootstrap node-image-pull service then fails with manifest unknown.
Reproduction
- Run kcli on an arm64 client.
- Connect it to a remote x86_64 KVM provider.
- Start an OKD 4.21 installation.
- Observe the bootstrap failure while pulling the architecture-suffixed release image.
Expected behavior
OKD should keep the valid release image configured by its installer without adding an architecture suffix.
Validation
Skipping the cross-architecture release override for OKD allowed the 4.21 installation to complete successfully through Install complete!.
Description
An OKD installation fails during bootstrap when kcli runs on an arm64 client connected to a remote x86_64 KVM host.
Root cause
kcli detects that the client and KVM host architectures differ and sets
OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDEusing the target architecture. The same tag construction is currently used for OCP and OKD, but OKD SCOS release tags do not have an architecture suffix.For OKD 4.21, kcli changes the valid release image:
into the nonexistent image:
The bootstrap
node-image-pullservice then fails withmanifest unknown.Reproduction
Expected behavior
OKD should keep the valid release image configured by its installer without adding an architecture suffix.
Validation
Skipping the cross-architecture release override for OKD allowed the 4.21 installation to complete successfully through
Install complete!.