You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bc35536
Browse filesBrowse the repository at this point in the historyBrowse files
fix(http-boot): stop requeue loop on UKI resolution failure
When constructUKIURL fails with a non-retryable error (e.g. image has no
UKI layer, registry validation error), the controller was returning the
error directly, causing controller-runtime to immediately requeue the
object. This produced a tight loop hammering the container registry.
Two changes:
- HTTP 429 responses from the registry are detected via isRegistryRateLimited
and retried with a 30s backoff instead of immediately.
- All other hard errors (no UKI layer, unknown image format, etc.) are
recorded in the ServerBootConfiguration status via PatchServerBootConfigWithError
and then return nil so no requeue occurs. Reconciliation resumes only
when the object is updated (e.g. the image field changes).
Signed-off-by: Andrew Dodds <andrew.dodds@sap.com>
0 commit comments