-
Notifications
You must be signed in to change notification settings - Fork 33
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
xenorchestra_vm
unable to set blocked_operations
on creation
#318
Comments
I thought this would be an easy fix since the xenstore data is already applied separately from the Here is the diff I tried
And here is the error from that attempt:
|
I was about to create an new issue, but then I found this one. For my case, I was playing around with the provider(appreciate the time you put into it 🫡 ), when I run into the same thing. Below is the error log ...
│ Error: jsonrpc2: code -32000 message: INTERNAL_ERROR((Failure "Unknown tag/contents")): {"code":"INTERNAL_ERROR","params":["(Failure \"Unknown tag/contents\")"],"call":{"method":"VM.remove_from_blocked_operations","params":["OpaqueRef:3009c1fc-6023-4ca4-af37-a380bd0a8269","true"]},"message":"INTERNAL_ERROR((Failure \"Unknown tag/contents\"))","name":"XapiError","stack":"XapiError: INTERNAL_ERROR((Failure \"Unknown tag/contents\"))\n at Function.wrap (file:///etc/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12)\n at file:///etc/xen-orchestra/packages/xen-api/transports/json-rpc.mjs:38:21\n at runNextTicks (node:internal/process/task_queues:60:5)\n at processImmediate (node:internal/timers:454:9)\n at process.callbackTrampoline (node:internal/async_hooks:130:17)"}
│
│ with xenorchestra_vm.instance["node-13"],
│ on main.tf line 65, in resource "xenorchestra_vm" "instance":
│ 65: resource "xenorchestra_vm" "instance" {
│
╵
exit status 1 Not sure if this is going to help, but anyway, a workaround at least for me was to:
|
The
xenorchestra_vm
resource has supportedblocked_operations
, however, our test suite has only been exercising the logic to update a VM to add and remove operations (source).When a VM is created from scratch the XO api serves the following error:
We should add test coverage for this case and fix the bug.
The text was updated successfully, but these errors were encountered: