Skip to content

Sync CNV runbook HCOGoldenImageWithNoArchitectureAnnotation.md (Updated at 2026-02-03 12:16:09 +0000 UTC) #393

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hco-bot wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Sync CNV runbook HCOGoldenImageWithNoArchitectureAnnotation.md (Updated at 2026-02-03 12:16:09 +0000 UTC) #393

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions ...openshift-virtualization-operator/HCOGoldenImageWithNoArchitectureAnnotation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ alert for this specific DICT.

This alert triggers when the golden image created for this DICT does not have a
defined architecture. If this image is used as a boot image for a virtual
machine (VM), and the VM will is scheduled on a node with a CPU architecture
different than the image architecture, the VM fails to start.
machine (VM), and the VM is scheduled on a node with different CPU architecture
than the image architecture, the VM fails to start.

## Diagnosis

Expand Down Expand Up @@ -79,15 +79,16 @@ User-defined DICTs are defined in the `HyperConverged` CR, in the
[podman manifest inspect
documentation](https://docs.podman.io/en/latest/markdown/podman-manifest-inspect.1.html).

If the image is a multi-architecture manifest ("fat manifest"), it includes the
If the image is a multi-architecture manifest ("fat manifest"), it includes
the
`manifests` field, which is a list of architectures supported by the image. If
the image is not a multi-architecture manifest, you need to find out what
is its architecture.

2. Edit the `HyperConverged` CR to add the missing
`ssp.kubevirt.io/dict.architectures` annotation.

The format of the annotation is a comma-separated list of architectures,
The format of the annotation is a comma-separated list of architectures,
for example: `amd64,arm64,s390x`.

3. If the image does not support any of the architectures supported by the
Expand All @@ -99,5 +100,5 @@ by the cluster, or remove the DICT from the `HyperConverged` CR.
documentation](https://docs.podman.io/en/latest/markdown/podman-manifest-create.1.html).

If you cannot resolve the issue, log in to the
[Customer Portal](https://access.redhat.com) and open a support case,
[Red Hat Customer Portal](https://access.redhat.com) and open a support case,
attaching the artifacts gathered during the diagnosis procedure.