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
There seems to be a limitation with the ibm_container_vpc_cluster data lookup when using wait_till = "Normal". Since terraform does a data lookup for every operation (plan, apply, destroy), if the cluster is not in a Normal state for whatever reason, the data lookup eventually times out and it blocks the terraform operation from occurring: Error: timeout while waiting for state to become 'normal' (last state: 'warning', timeout: 30m0s)
A use case we keep seeing is that after cluster has been initially deployed, we see it goes into a Warning state:
"state": "warning",
"status": "Some Cluster Operators are down-level and need to be updated, see 'https://ibm.biz/rhos_clusterversion_ts'",
While in this state, the data lookup will fail. And we are seeing some clusters getting stuck in this state, meaning terraform can no longer manage the cluster.
According to the terraform docs, Normal is supposed to ignore the critical and warning states. did something change here?
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform CLI and Terraform IBM Provider Version
tf 1.9
provider 1.74.0
Affected Resource(s)
ibm_container_vpc_cluster
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
There seems to be a limitation with the ibm_container_vpc_cluster data lookup when using
wait_till = "Normal"
. Since terraform does a data lookup for every operation (plan, apply, destroy), if the cluster is not in aNormal
state for whatever reason, the data lookup eventually times out and it blocks the terraform operation from occurring:Error: timeout while waiting for state to become 'normal' (last state: 'warning', timeout: 30m0s)
A use case we keep seeing is that after cluster has been initially deployed, we see it goes into a Warning state:
While in this state, the data lookup will fail. And we are seeing some clusters getting stuck in this state, meaning terraform can no longer manage the cluster.
According to the terraform docs, Normal is supposed to ignore the critical and warning states. did something change here?
Community Note
Terraform CLI and Terraform IBM Provider Version
tf 1.9
provider 1.74.0
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
https://github.com/terraform-ibm-modules/terraform-ibm-scc-workload-protection-agent/blob/main/solutions/standard/provider.tf
Debug Output
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: