-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terraform provider: flapping branch state when combined with other updates #13363
Comments
What's the log when it fails? |
That is the failing / incorrect log. Previously, renovate opened the PR with two changed files ( The
But the Terraform manager does not, and changes files:
Afterwards, only this one file is committed and incorrectly force-pushed on the branch. Compare the original commit with the force-pushed commit. One contains correctly both updates, the other one only the terraform provide update but not the regex update. On the next run, renovate will correct the branch and incomplete it again on the following and so on. If you like, I can trigger more example runs (and also leave it in the "correct" state if you prefer). |
Just hit this issue - self-hosted renovate 32.232.0, terraform manager. We have a monorepo and a few package rules grouping terraform manager updates, like so:
with |
Hi there, Get your issue 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. To get started, please read our guide on creating a minimal reproduction. We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment. Good luck, The Renovate team |
@rarkins The linked repository still outlines the issue. We are still observing it with that configuration on our self-hosted instance. |
branch.isUpToDate() will return true unless the list of packages/versions changes in the branch. There's no expiry on that. You can force override that by ticking the rebase/retry checkbox in any PR. |
Thanks. So it should be fixed. I will look out for the next PR for our self-hosted installation and close / update the ticket accordingly. |
Just so I understand, do you mean that you turned on |
It was not. Your response didn't include that it is driven by But now, I suspect I have to? The reproducible repository is apparently no longer sufficient — so a |
If the hosted app doesn't reproduce the problem (because it uses |
I have just check running renovate (v34.50.0) without a (persistent) branch cache on the linked reproducible repository. And it still triggers this issues (the branch is updated to only include the terraform artifact update without the regex terraform bump). Log of the second renovate run (branch is actually up-to-date but still partially rebuild)
|
When a bug has been marked as needing a reproduction, it means nobody can work on it until one is provided. In cases where no reproduction is possible, or the issue creator does not have the time to reproduce, we unfortunately need to close such issues as they are non-actionable and serve no benefit by remaining open. This issue will be closed after 7 days of inactivity. |
I have classified this as low priority if it only occurs when grouping AND with regex manager |
How are you running Renovate?
Self-hosted, but reproduced with RenovateApp on GitHub
If you're self-hosting Renovate, tell us what version of Renovate you run.
31.15.0
Please select which platform you are using if self-hosting.
github.com
If you're self-hosting Renovate, tell us what version of the platform you run.
No response
Describe the bug
Terraform provider updates with rangeStrategy
update-lockfile
are unreliable when grouped with other updates (like a regex manager to update the Terraform version). Renovate flaps the branch between the complete updates and only the Terraform artifacts updates.I stumbled across this with self-hosted renovate but was able to reproduce it with the renovate app on Github, too. See msw-kialo/renovate-flapping-grouped-terraform-updates#1 for a reproduction and a sample PR.
Furthermore, it makes it impossible to request the upgrade out-of-schedule if
prCreation
is set tonot-pending
: it would require two runs with the same outcome. This way I encountered it the first time. But that is not really relevant to me (although it made debugging/testing it more challenging).Relevant debug logs
Logs
https://app.renovatebot.com/dashboard#github/msw-kialo/renovate-flapping-grouped-terraform-updates/545881011
Effect msw-kialo/renovate-flapping-grouped-terraform-updates#1
Note the difference between
2 file(s) to commit
and the wrong commit that only includes the one artifact file.Have you created a minimal reproduction repository?
I have linked to a minimal reproduction repository in the bug description
The text was updated successfully, but these errors were encountered: