1. 1. Build Details

• *Job*: build-node-image
• *Build #*: 1956
• *Stream*: 4.19-9.6
• *Timestamp*: 2026-01-22T09:50:03 UTC
• *Duration*: 11 minutes
• *Jenkins URL*: https://jenkins-rhcos--prod-pipeline.apps.int.prod-stable-spoke1-dc-iad2.itup.redhat.com/job/build-node-image/1956/

1. 1. Root Cause
      *Podman container cleanup error during extensions container build*

The build failed on both *x86_64* and *s390x* architectures with the same error during the extensions container build stage. The container image was successfully built and committed, but podman failed to delete the build container afterward, causing the overall build to fail.

1. 1. 1. Error Message
         ```
         time="2026-01-22T10:01:37Z" level=error msg="error deleting build container \"171c54860030d5437299a67a33110a9e68c2ee8147a95958b0078da9f0d056fc\": identifier is not a container\n"
         Error: identifier is not a container

subprocess.CalledProcessError: Command '['podman', 'build', ...]' returned non-zero exit status 125.
failed to execute cmd-remote-build-container: exit status 1
```

1. 1. 1. Affected Architectures

         Architecture	Result
         --------------	--------
         x86_64	❌ Failed (identifier is not a container)
         s390x	❌ Failed (identifier is not a container)
         aarch64	✅ Success
         ppc64le	(unknown - likely success based on log ordering)

1. 1. 1. Key Observations
         1. The container image was *successfully built and tagged* before the error occurred
         2. The error happens during podman's cleanup phase when trying to delete the build container
         3. This appears to be a podman bug or race condition, not an actual build failure
         4. Exit status 125 is a podman-specific error code

1. 1. Source
      The failure occurs in:

• *Script*: `/usr/lib/coreos-assembler/cmd-remote-build-container`
• *Line 48*: `runcmd(cmd)` calling podman build

1. 1. Potential Causes
      1. Race condition in podman container cleanup
      2. Podman version incompatibility
      3. Storage driver issues on specific architectures

1. 1. Resolution

• *Status*: Needs retry
• *Action*: May need investigation if failure persists across retries