[IKRedHat]

Summary

Adds RELATED_IMAGE_RHAII_VLLM_CPU_PZ_* entries to the ClusterServiceVersion manifest to resolve ImagePullBackOff blocker (RHOAIENG-88193) and enable proper digest injection by OLM for the vLLM CPU Power/Z runtime template.

Context

This PR is part of the vLLM CPU Power/Z AIPCC migration (RHAI-121 Epic, RHAISTRAT-2304 parent). Related PRs have already merged:

• opendatahub-operator chore(deps): update odh-operator-v2-16 to c25703d #3996 (RHAI-455) — Added RELATED_IMAGE_RHAII_VLLM_CPU_PZ_* environment variable declarations to handler.go
• odh-model-controller chore(deps): update odh-operator-v2-17 to f2524cd #925 (RHAI-455) — Switched vllm-cpu-runtime-template from $(vllm-cpu-image) to $(vllm-cpu-pz-image)

However, the CSV is currently missing these entries, causing the template parameter to resolve to a placeholder digest instead of the actual multi-arch image. This blocks P/Z deployment with ImagePullBackOff errors.

Changes

Adds three new entries to bundle/additional-images-patch.yaml:

• RELATED_IMAGE_RHAII_VLLM_CPU_PZ_IMAGE
• RELATED_IMAGE_RHAII_VLLM_CPU_PZ_FAST_1_IMAGE
• RELATED_IMAGE_RHAII_VLLM_CPU_PZ_FAST_2_IMAGE

All entries use the x86 CPU image digest as a placeholder, following the atomic swap pattern established during vLLM Gaudi AIPCC migration (RHAI-120, PR #18857).

Test Plan

• Verify CSV generation includes the new RELATED_IMAGE entries
• Confirm vllm-cpu-runtime-template resolves to actual digest (not placeholder)
• Deploy on P/Z hardware once image is available (RHAI-457)

Resolves: RHAI-456
Parent Epic: RHAI-121
Blocker: RHOAIENG-88193

[IKRedHat]

Closing per EA2 retarget decision from Edward Quarme (Aug 26) — the IBM team found a torch.compile runtime error on s390x during validations that blocks the vLLM CPU P/Z AIPCC migration for 3.6-EA1.

EA1 fallback: 3.6-EA1 will ship the existing 3.5 GA Power/Z CPU image (registry.redhat.io/rhoai/odh-vllm-cpu-rhel9:v3.5.0-1786557544) instead of the AIPCC-built image. The existing vllm-cpu-image → RELATED_IMAGE_ODH_VLLM_CPU_IMAGE path continues to work, so no changes needed for EA1.

EA2 target: The AIPCC migration moves to 3.6-EA2. PR #30868 (targeting rhoai-3.6-ea.2 branch) remains open and valid for the new timeline once blocker RHAI-706 (torch.compile fix + AIPCC rebuild) is resolved.

See full context in team-openshift-ai-serving-runtimes Slack thread: https://redhat-internal.slack.com/archives/C07A8ECBTPB/p1787759839628969