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_cluster_config data source is broken in 1.25 release #2651

Closed
dprosper opened this issue May 19, 2021 · 5 comments · Fixed by #2661
Closed

ibm_container_cluster_config data source is broken in 1.25 release #2651

dprosper opened this issue May 19, 2021 · 5 comments · Fixed by #2661
Labels
service/Kubernetes Service Issues related to Kubernetes Service Issues

Comments

@dprosper
Copy link
Contributor

dprosper commented May 19, 2021

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

$ terraform -v
Terraform v0.15.1
on windows_amd64
+ provider registry.terraform.io/hashicorp/external v2.1.0
+ provider registry.terraform.io/hashicorp/helm v2.1.2
+ provider registry.terraform.io/hashicorp/kubernetes v2.2.0
+ provider registry.terraform.io/hashicorp/null v3.1.0
+ provider registry.terraform.io/hashicorp/time v0.7.1
+ provider registry.terraform.io/ibm-cloud/ibm v1.25.0
+ provider registry.terraform.io/sysdiglabs/sysdig v0.5.14

Your version of Terraform is out of date! The latest version
is 0.15.3. You can update by downloading from https://www.terraform.io/downloads.html

Affected Resource(s)

  • ibm_container_cluster_config

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please share a link to the ZIP file.

data "ibm_container_cluster_config" "clusterConfig" {
  cluster_name_id   = var.cluster_id
  resource_group_id = data.ibm_resource_group.group.id
  config_dir        = "/tmp"
}

Debug Output

image

Expected Behavior

The same exact code works fine in the provider release versions 1.24.0 nd 1.23.2

Actual Behavior

It fails with the error seen above in the provider version 1.25.0

Steps to Reproduce

  1. add the code snippet above and run...
  2. terraform apply
@dprosper
Copy link
Contributor Author

dprosper commented May 19, 2021

In addition, when I run the code with 1.25.0 of the provider, the following files are created in the /tmp folder relevant to the cluster:
image

when running the same template with 1.24.0 of the provider, the following files are created in the /tmp folder relevant to the cluster:
image

@kavya498 kavya498 added the service/Kubernetes Service Issues related to Kubernetes Service Issues label May 20, 2021
@kavya498
Copy link
Collaborator

@dprosper,
Looks like cluster config is able to download but it has failed due to some permission issue..
Error says process cannot access the file because it is been used by other another process
Do you have any parallel process which is trying access the folder while the cluster config datasource is running?

@dprosper
Copy link
Contributor Author

possibly, anti-virus or Terraform itself, but what is weird is this is working with earlier version of the provider, I reverted to version 1.24.0.

@kavya498
Copy link
Collaborator

I couldn't reproduce this issue on my machine (macOS)

@dprosper
Copy link
Contributor Author

can I ask you to ping me on Slack @dimitri_prosper ?

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

Successfully merging a pull request may close this issue.

2 participants