-
Notifications
You must be signed in to change notification settings - Fork 676
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
Error downloading the cluster config - config.zip: no such file or directory #2806
Comments
Looks like you are running two configs on same cluster..
|
@kavya498 - In the scenario where 3rd party modules are used, it is not possible for someone assembling multiple modules together to change the "ibm_container_cluster_config" "cluster" block. I think the IBM Cloud Provider should handle transparently this without requiring specific config_dir to be set. |
Using |
Since it is a parallel process, this is happening..We ll look into issue |
This may have been a side effect of the race conditions that were fixed in IBM-Cloud/bluemix-go#318 |
No joy, when we remove the workaround, we reproduce the issue:
For now, we will continue to use the workaround (aka provide different |
Opened a PR at IBM-Cloud/bluemix-go#328 that appears to fix the issue. |
@kavya498 We have found an issue with the workaround... If you specifically specify a
However, if you do not use Can you help push to get IBM-Cloud/bluemix-go#328 merged so we can stop using the broken workaround? Thanks |
@ocofaigh we are reviewing PR and will be available part of next week release |
So the reason we were seeing the issue described in above comment where kubeconfig was not getting re-generated when using So what we need to do to ensure we don't hit either of the issues is, for the value of
|
Latest updates on the permanent fix -> IBM-Cloud/bluemix-go#328 (comment) |
Fix looks good in v1.35.0 (#3264). Closing |
We hit a scenario where when two data sources (both running
ibm_container_cluster_config
) run at the same time, they seem to clash with each other and give the below error:Community Note
Terraform CLI and Terraform IBM Provider Version
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.
Debug Output
Panic Output
Expected Behavior
The provider should be able to handle such a scenario and not produce an error
Actual Behavior
The following error:
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: