You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a possibility to add volatile disk to opennebula_virtual_machine resource, which shares the virtual machine's lifecycle. The documentation says that if size disk size value is changed on an existing resource, it must be bigger than the previous one.
If the new value is still smaller than the previous one, on "terraform apply", the plugin crashes producing a huge error log:
Stack trace from the terraform-provider-opennebula_v1.3.0 plugin:
panic: runtime error: index out of range [1] with length 1
Error: The terraform-provider-opennebula_v1.3.0 plugin crashed!
This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.
Terraform and Provider version
Terraform v1.6.2
OpenNebula provider v1.3.0
Affected resources and data sources
opennebula_virtual_machine
Terraform configuration
No response
Expected behavior
Error is raised by the plugin telling that the disk size value should be bigger than the previous one.
Actual behavior
The plugin crashes.
Steps to Reproduce
Create "opennebula_virtual_machine" resource with raw disk of a random size, e.g. using sample:
This issue is stale because it has been open for 30 days with no activity and it has not the 'status: confirmed' label or it is not in a milestone. Remove the 'status: stale' label or comment, or this will be closed in 5 days.
This issue is stale because it has been open for 30 days with no activity and it has not the 'status: confirmed' label or it is not in a milestone. Remove the 'status: stale' label or comment, or this will be closed in 5 days.
Description
There is a possibility to add volatile disk to opennebula_virtual_machine resource, which shares the virtual machine's lifecycle. The documentation says that if size disk size value is changed on an existing resource, it must be bigger than the previous one.
If the new value is still smaller than the previous one, on "terraform apply", the plugin crashes producing a huge error log:
Terraform and Provider version
Terraform v1.6.2
OpenNebula provider v1.3.0
Affected resources and data sources
opennebula_virtual_machine
Terraform configuration
No response
Expected behavior
Error is raised by the plugin telling that the disk size value should be bigger than the previous one.
Actual behavior
The plugin crashes.
Steps to Reproduce
terraform plan; terraform apply
)terraform plan; terraform apply
) (multiple times if needed)Debug output
No response
Panic output
No response
Important factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: