"Disallowed variable names in template" logspam since #30892 #31031
Replies: 2 comments
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
It appears the log spam was caused by an expired token, which prevented Renovate from accessing our private container registry. After regenerating the token and updating the corresponding host rule, the issue resolved. However, the "Disallowed variable names in template" errors obscured the actual HTTP errors. |
Beta Was this translation helpful? Give feedback.
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitLab
Please tell us more about your question or problem
After upgrading from Renovate 38.42.0 to 38.43.0, which is where #30892 got introduced we get a lot of logspam, even with a very simple config like the follows:
See relevant logs below. There were no issues prior to 38.43.0. If necessary I'll prepare a minimal reporoduction repo.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions