-
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
resources updates not applied #63
Comments
Seeing the same issue |
Hi, Context update are not taken into account. |
@jaypif - in newer OpenNebula releases (about 5.4+ or so) the context can be updated any time, even when the VM is running. Destroy and recreate is no longer needed. That said, the context is provided in form of an IDE CD, which does not support hotplug in Linux. So the guest cannot be notifed about the context change. But as soon as it mounts the context CD (or reboots inside the same qemu process - no undeploy/deploy is needed), the new context becomes visible. So it would be nice to have the context changes from terraform resource propagated into the ONe state. My use case is especially the |
Hello, I can confirm that the Context Update on running VMs now works from the OpenNebula UI, but this does not works from Terraform. Sadly I don't code in Go so I doubt I will be able to implement a fix for this problem. |
@jaypif Is there any guidance on the turn around time around this issue? |
I cannot commit on an ETA as the maintenance of the provider is performed when we have some bandwidth to do it. I hope it will be possible to have some time to take a deep view on it in the coming weeks. I let you know. Thanks |
Thanks for the update @jaypif |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Resource updates are marked as applied in the plan even when not applied on the cloud provider.
We don't handle if a part could be updated or not there is no check, and there is no documentation.
Here's the quote from a team member on the problem:
The text was updated successfully, but these errors were encountered: