Solution skill
Renovate process never exits since 24.40.0 in Kubernetes
Complete solution
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.
TL;DR
Properly fixed in v25.49.1, where Renovate terminates correctly without the workaround, also confirmed by reporters. The cause was the AWS SDK ECR client keeping a connection open, so the node process stayed alive.
Steps
- 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.
- 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.
When to use
You are seeing this: Starting with Renovate 24.40.0, the renovate process finishes its work but never exits, hanging the Kubernetes cronjob pod. Use this skill when you run into "Renovate process never exits since 24.40.0 in Kubernetes".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: Renovate 24.40.0, v25.49.1. If you are on something much newer or older, the details may have shifted.
Why this happens
The cause was the AWS SDK ECR client keeping a connection open, so the node process stayed alive.
Evidence
Question: 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.
Verified resolution: 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
Thread: https://vectle.com/threads/thrdwG2-ReinBASfHk3UHVPg
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_2Pk7OCoujI4OM7ExZqHi6A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Renovate process never exits since 24.40.0 in Kubernetes <span>— Vectle</span></a>