-
Notifications
You must be signed in to change notification settings - Fork 479
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
VM scheduled actions via Sunstone 3/3: Unexpected behavior on VMs older than a month when clicked #5209
Comments
@rsmontero, @tinova, I think this is very important if not critical... |
Hello @atodorov-storpool, Just FYI, we call charters to "the blue thing". You can find the docs here: http://docs.opennebula.io/5.12/operation/vm_management/vm_instances.html?highlight=charters#vm-charter Regarding the bugs you mentioned:
|
Sure @christian7007. here it is Clicked on the charters in ~17:38:25
Ammm it looks like the scheduler become crazy after first try with VM 6 (when reproduced the problem for reporting)...
|
for faster reproduction I'am instantiating a VM, undeploy, then editing /VM/STIME to make the VM older, then resume the VM, and click on the charter Same reproduced and in a customer installation too - I had a testing VM left from the initial tests. just resumed the VM to become in running state, clicked on the charter and the VM was almost immediately in state6 (DONE) |
And The VM XML in question before clicking on the charter:
|
Thanks! Will disable them in the customer installations until this is resolved. |
I've been looking into it and it seems that the root cause is that the scheduled actions used are relative actions (which are relatives to the VM creation time). I've discussed this with the team and we thing that the following improvements should be added:
Also, thank you very much for the feedback! Really nice catch! |
Hi @christian7007,
|
Hello @atodorov-storpool, thanks again for the feedback. We'll take this into account when fixing this issue. |
Signed-off-by: Jorge Lobo <jlobo@opennebula.io>
Signed-off-by: Jorge Lobo <jlobo@opennebula.io>
Signed-off-by: Jorge Lobo <jlobo@opennebula.io>
Signed-off-by: Jorge Lobo <jlobo@opennebula.io>
Signed-off-by: Jorge Lobo <jlobo@opennebula.io>
Signed-off-by: Jorge Lobo <jlobo@opennebula.io>
Description
(bug 3/3)
Not sure how to name the blue "thing" next to the green "Add Action" button but it has a lot of troubles...
When you click on it two actions are defined without a warning or confirmation - just committed to the core...
To Reproduce
Perform the following on a VM that was instantiated more than a month ago:
Expected behavior
Not sure what I expect here:
Details
Additional context
Missing a warning even every operator could click there and terminate a production VM in a glipse...
Please note that I totally agree that this case is hard to catch with common CI/automated testing because usually the testing VMs are not older enough to catch this. I had the chance to play with a staging environment where i have older VMs.
Progress Status
The text was updated successfully, but these errors were encountered: