-
Notifications
You must be signed in to change notification settings - Fork 666
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
Terraform Crashes #1701
Comments
@surajsub ^^^ |
Hmm - it should not crash.. do you have your key loaded on the service instance. I'll take a deeper look at it |
what resource are you trying to provision |
We are trying to create VSI |
This works fine with London, Toronto regions so I believe the key part should be fine. |
After looking at the crash logs found that the index out of bound error here: https://github.com/IBM-Cloud/terraform-provider-ibm/blob/master/ibm/data_source_ibm_pi_public_network.go#L71
This was failing because there were no public networks here. As a workaround I create a LPAR manually which creating the public network for me. Feel that this should be taken care in the provider code to handle the failure when public network does not exist initially. |
The power instance does not create a public network when a new instance is created . The public network is created only when 1st pvm instance is created.. It's a chicken and egg problem. I will discuss with the power team. |
Hi @surajsub Can we have something like a flag for public ip |
Another suggestion is to create the public network if does not exist using |
Fixed the crash.. |
terraform apply results in crash on PowerVS - Washington and Dallas region.
Terraform Version
Terraform v0.12.20
Affected Resource(s)
Panic Output
crash.log
Expected Behavior
What should have happened?
terraform apply
command should have worked fine.Actual Behavior
What actually happened?
terraform apply
command results in a crash.Steps to Reproduce
terraform apply
Important Factoids
The text was updated successfully, but these errors were encountered: