-
Notifications
You must be signed in to change notification settings - Fork 10
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
Adding a VM attached to a manual network from a Template to an existing environment causes Terraform to crash #29
Comments
Hello @ThisMayActuallyBeTyler Thank you for the detail report, we didn't consider manual networks for the MVP of the connector, but unfortunately, we have considered the case where the manual network come from the template. There isn't an acceptance test validating this scenario. An acceptant test should be added as part of this ticket. Regards. |
Hi James. I talked with Tyler and got the steps to reproduce this issue. They are as documented above. Steps to Reproduce
Here is my code:
Here is the result:
Because I cannot share the template with your account, you will have to go through the steps to reproduce yourself. I can assist w/ that. We can chat tomorrow. Also, I am still running the code I built, equal to v0.10
|
👍 |
Terraform Version
This was also attempted by other users on v0.11.13
Affected Resource(s)
func flattenNetworkInterface(v skytap.Interface) map[string]interface{} {
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Terraform should add a VM from a template to the designated environment regardless of automatic or manual networks.
Actual Behavior
It seems like adding a VM connected to a manual network to an existing environment in Terraform causes Terraform to crash. The environment and corresponding add VM functionaility completes in Skytap as expected. However, Terraform crashes despite the process completing within Skytap
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
This may be related to "null" values retrieved in the "interfaces" section of JSON retrieved for a VM with one NIC on a manual network
The text was updated successfully, but these errors were encountered: