Skip to content
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

ibm_container_vpc_cluster data lookup fails when using wait_till = "Normal" if cluster has a warning #5922

Open
ocofaigh opened this issue Jan 16, 2025 · 0 comments
Labels
service/Kubernetes Service Issues related to Kubernetes Service Issues

Comments

@ocofaigh
Copy link
Contributor

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?

Image

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.

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

  1. terraform apply

Important Factoids

References

  • #0000
@github-actions github-actions bot added the service/Kubernetes Service Issues related to Kubernetes Service Issues label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/Kubernetes Service Issues related to Kubernetes Service Issues
Projects
None yet
Development

No branches or pull requests

1 participant