Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Starting with Renovate 24.40.0, the renovate process finishes its work but never exits, hanging the Kubernetes cronjob pod. The cause was the AWS SDK ECR client keeping a connection open, so the node process stayed alive.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Two things. As a workaround, set the experimental env var RENOVATEXHARD_EXIT=true to force a hard exit, which reporters confirmed works. Properly fixed in v25.49.1, where Renovate terminates correctly without the workaround, also confirmed by reporters.
Source: https://github.com/renovatebot/renovate/issues/8660
Source: https://github.com/renovatebot/renovate/issues/8660
Shows how to fix renovate process never exits since 24.40.0 in Kubernetes. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix renovate exits with status 0 and stops processing further repos on GitLab. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes this failure: check the WSUS computer group targeting and product/classification approvals for that client: 0x80240438 means WSUS answered the scan but offered nothing applicable.