Roman Iuvshyn

yeah, you are right, but the change is applied via terraform, I was running tests doing the same change to the same cluster (initially provisioned by terraofrm) but via rancher...

I should try to reproduce this with just dummy `rancher2_cluster_v2` without even nodes I have feeling it will have the same issue.

Well if this issue will be reproduced that would clearly highlight that there is a bug in provider or API it uses. obviously that is not going to be usable...

hmm, I am abit confused. what is the purpose then of `rancher2_cluster_v2` resource?

I want to use `rancher2_cluster_v2` resource to build rancher managed rke2 cluster. Once the cluster is created then I am getting node-command from that resource like that `rancher2_cluster_v2.this.cluster_registration_token[0].node_command` and passing...

@weiyentan > That means you are adding it for terraform to do the initial add but once it is built by right because rancher fleet is managing it any changes...

@jakefhyde thanks for looking in to this. Sometimes it takes up to 20 iterations or more to reproduce. here is my `rancher2_cluster_v2`: I've dropped `additional_manifest ` as I was able...

@jakefhyde nope, that was enough for me to reproduce it. do you have machines in your cluster? It might be related to the fact that I am not using `machine_pools`...

@jakefhyde yeah... I never got cluster deleted as it was never deleted the bootstrap machine for some reason it got stuck on it. however in rancher logs every time I...

having exactly same issue. but for me it is more constant than random failures. I was trying to upgrade k3s from current version `v1.21.11+k3s1` where I don't have such issues...