-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.19.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
Generating an IBU seed image on a SNO 4.19.0-ec.1 succeeds, but the SeedGenerator CR is in a failed state, specifically: - lastTransitionTime: "2025-01-30T10:15:47Z" message: 'Seed generation failed: imager container status check failed: expected container status exited, found: stopped' Seed image generation is executed via systemd-run and a container (podman run). LCA expects the container's exit code to be 0 (success) and its status to be 'exited', but in this case the status is shown as 'stopped'. The latter leads to the SeedGenerator CR being in a failed state, although the respective seed image generation container succeeded.
Version-Release number of selected component (if applicable):
OCP 4.19.0-ec.1 $ podman version Client: Podman Engine Version: 5.3.1 API Version: 5.3.1 Go Version: go1.23.2 (Red Hat 1.23.2-1.el9) Built: Wed Nov 27 12:10:02 2024 OS/Arch: linux/amd64 $ systemctl --version systemd 252 (252-49.el9)
How reproducible:
100%
Steps to Reproduce:
1. Setup an SNO 4.19.0-ec.1
2. Install LCA
3. Generate an IBU seed container image
Actual results:
The seed image generation command is successful, but the SeedGenerator CR is in a failed state.
Expected results:
The seed image generation command is successful and the SeedGenerator CR is in its success state.
Additional info:
- links to
-
RHEA-2025:144989
OpenShift Container Platform 4.19.0 IBU extras update
- mentioned on