You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation states, that if the cluster_id of a nodegroup changes, the nodegroup will be recreated.
Actually, terraform tries to reattach the nodegroup by updating the cluster_id in place.
Cluster gets replaced, therefore cluster will have a new id
After terraform recreated the cluster, it tries to update the nodegroup with the new ID of the parent cluster. This won't work, as you cannot attach an existing nodegroup to a new cluster.
Actual Behavior
Terraform detects the change of cluster ID and replaces the nodegroup with a new one.
Steps to Reproduce
terraform apply -replace "path.to.parent.cluster"
Possible Solution
I'm not too deep into the sourcecode, but I guess the ForceNew property of cluster_id must be set to true.
The documentation states, that if the
cluster_id
of a nodegroup changes, the nodegroup will be recreated.Actually, terraform tries to reattach the nodegroup by updating the
cluster_id
in place.Terraform Version
1.4.2, shouldn't be related to version.
Affected Resource(s)
openstack_containerinfra_nodegroup_v1
Terraform Configuration Files
Expected Behavior
Cluster gets replaced, therefore cluster will have a new id
After terraform recreated the cluster, it tries to update the nodegroup with the new ID of the parent cluster. This won't work, as you cannot attach an existing nodegroup to a new cluster.
Actual Behavior
Terraform detects the change of cluster ID and replaces the nodegroup with a new one.
Steps to Reproduce
terraform apply -replace "path.to.parent.cluster"
Possible Solution
I'm not too deep into the sourcecode, but I guess the
ForceNew
property ofcluster_id
must be set to true.https://github.com/terraform-provider-openstack/terraform-provider-openstack/blob/main/openstack/resource_openstack_containerinfra_nodegroup_v1.go#LL45C10-L45C10
The text was updated successfully, but these errors were encountered: