Build Details

Root Cause Analysis

The build failed because the Kubernetes cluster exceeded its CPU quota when trying to launch pods.

Error Message

Failure executing: POST at: [https://172.30.0.1:443/api/v1/namespaces/rhcos\-\-prod\-pipeline/pods|https://172.30.0.1:443/api/v1/namespaces/rhcos--prod-pipeline/pods].
Message: pods "pod\-f52cdf84\-cc2f\-469a\-83d1\-a253643cae18\-nrnw2\-v566x" is forbidden:
exceeded quota: rhcos\-\-notterminating, requested: requests.cpu=2, used: requests.cpu=30850m, limited: requests.cpu=32

Analysis

This is a transient infrastructure issue. The OpenShift cluster hosting the Jenkins pipeline had too many concurrent jobs running and hit its CPU resource quota limit (32 CPU cores). The build couldn't schedule new pods.

The build was triggered by upstream build #3445.

Resolution

This is a transient flake - retry the build when cluster resources are available. Consider:
1. Monitoring cluster resource usage
2. Adjusting quota limits if this becomes frequent
3. Implementing better job scheduling/queuing