-
Notifications
You must be signed in to change notification settings - Fork 52
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
Plugin crashes when trying to decrease virtual machine's raw disk size #500
Comments
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. |
Up |
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. |
I think it would be better to fix this at the same time we externalize the disk resource as it's not a critical bug |
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: