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 with no default worker pool crashes on destroy #1733

Closed
evpirnia opened this issue Jul 22, 2020 · 3 comments
Closed
Assignees

Comments

@evpirnia
Copy link

Archive.zip

Goal: Create a VPC Cluster with no default worker pool. I want to make my own worker pools.

Both the IBM Cloud CLI and UI allow me to delete the default worker pool and make my own worker pools. I tried to automate this task in terraform using the IBM Cloud terraform provider.

Attached you will find an archive of my code that performs the following actions:

  • Create a vpc cluster (a default worker pool will automatically be created as well)
  • Create an additional worker pool
  • Delete the default worker pool (in a null resource local-exec provisioner)

I am able to plan and apply. However, when I try to terraform destroy, terraform crashes (see destroy.log in archive).

The crash references the below function.

func resourceIBMContainerVpcClusterDelete(d *schema.ResourceData, meta interface{}) error {

Please note that I am using terraform v0.12.28 and the IBM Cloud terraform provider v1.8.1.

@hkantare
Copy link
Collaborator

hkantare commented Jul 29, 2020

We fixed the issue to fix the nil pointer exception when the default worker pool is removed
#1763

We added some check the element exists and read the value
The fix is available in master branch..It will be part of the next release

@evpirnia
Copy link
Author

Thank you @hkantare !!

@hkantare hkantare self-assigned this Aug 10, 2020
@evpirnia
Copy link
Author

Merged, closing! :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants