BenB196

I'm not really familiar with this code base, but looking at the merge request, I see that there is a test for [`set`](https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release#set) - https://github.com/hashicorp/terraform-provider-helm/pull/1097/files#diff-0c630859c0a0648a5a7cd178d9b8d011108f16648cd8fc6b651390cec95ebc56R1781-R1827 & https://github.com/hashicorp/terraform-provider-helm/pull/1097/files#diff-0c630859c0a0648a5a7cd178d9b8d011108f16648cd8fc6b651390cec95ebc56R2077-R2111, but none for...

Just an FYI, while there still might be a "bug" there is a workaround for this issue on `2.12.1`. If you're setting a chart version like: ```hcl version = "0.3.1"...

> > Just an FYI, while there still might be a "bug" there is a workaround for this issue on `2.12.1`. > > If you're setting a chart version like:...

Adding a comment here, this seems to also happen with integration policies when creating/updating a large number of them at the same time.

Hi @barkbay, sure here are the logs showing that the predicate was the active blocker; ```json {"log.level":"info","@timestamp":"2025-05-07T15:27:05.525Z","log.logger":"elasticsearch-controller","message":"Starting reconciliation run","service.version":"2.16.1+1f74bdd9","service.type":"eck","ecs.version":"1.4.0","iteration":"2888","namespace":"elastic-prod","es_name":"es-prod"} {"log.level":"info","@timestamp":"2025-05-07T15:27:05.863Z","log.logger":"elasticsearch-controller","message":"Ensuring no voting exclusions are set","service.version":"2.16.1+1f74bdd9","service.type":"eck","ecs.version":"1.4.0","iteration":"2888","namespace":"elastic-prod","es_name":"es-prod","namespace":"elastic-prod","es_name":"es-prod"} {"log.level":"info","@timestamp":"2025-05-07T15:27:06.311Z","log.logger":"elasticsearch-controller","message":"Cannot restart some nodes for...

Hmm, unfortunately, I didn't save the output of the cluster health command, and I don't recall if there were any relocating shards at the time, but the upgrade was also...

I thought about that before opening this issue, but I came to the conclusion that they were different enough to warrant a new issue. While #8429 observes a similar issue,...

> This behaviour has been in place for ~ 6 years Yep, and in the ~4 years I've been using ECK, this is also the first time I've really experienced...

I had opened some issues a while back under the integrations project, I only found one additional issue, https://github.com/elastic/integrations/issues/4880, but it's been a bit since I checked, not sure if...

Was anyone ever able to figure out what was causing this issue? Observing a similar error and it doesn't provide that great of context.