-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.22
-
None
-
None
-
False
-
-
None
-
Critical
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
Currently the IRI api checks that the ocp release bundle name does not exceed the 64 chars. This works for regularly released OCP payload (stable/nightly/CI streams), but it fails for Prow CI pre-submit jobs, where the ephemeral release payload name is usually greater than 64 chars.
Version-Release number of selected component (if applicable):
4.22
How reproducible:
Always
Steps to Reproduce:
1. Run a rehearsal/presubmit job based on e2e-agent-compact-ipv4-iso-no-registry workflow
Actual results:
During the installation, the process fails at 66% due a bootkube failure:
Feb 09 18:01:34 master-0 bootkube.sh[20013]: "internalreleaseimage.yaml": failed to create internalreleaseimages.v1alpha1.machineconfiguration.openshift.io/cluster -n : InternalReleaseImage.machineconfiguration.openshift.io "cluster" is invalid: [spec.releases[0].name: Too long: may not be more than 64 bytes, <nil>: Invalid value: null: some validation rules were not checked because the object was invalid; correct the existing errors to complete validation]
Expected results:
The installation must succeed
Additional info:
The CI generated name is 76 chars, ie ocp-release-bundle-4.22.0-0.ci-2026-02-09-204741-test-ci-op-phx0mrh8-latest
Thanks bfournie@redhat.com that discovered this issue
- blocks
-
OCPBUGS-76542 [release-4.21][Appliance] Fix IRI release max length to support CI jobs
-
- Closed
-
- is cloned by
-
OCPBUGS-76542 [release-4.21][Appliance] Fix IRI release max length to support CI jobs
-
- Closed
-
- links to