History etime is not set on shutdown timeout
|Assignee:||Carlos Martín||% Done:|
|Category:||Core & System|
|Target version:||Release 4.14.2|
|Affected Versions:||OpenNebula 4.12|
Bug reported in this thread:
I could reproduce the problem.
I had created a Windows 7 VM.
Then I wanted the VM to shutdown (not hard).
The VM at this point had no ACPI functionality and OpenNebula said "STATUS: SHUTDOWN".
Then I performed a SHUTDOWN HARD. OpenNebula said that this action was not allowed due to wrong status. Than I remowed the VM and the VM disappeared from onevm list.
Bug #4000: Fix history etime with onedb
(cherry picked from commit ee44b97013eee45e0a1ace90520832f93292e73e)
#1 Updated by Carlos Martín almost 5 years ago
- Status changed from Pending to New
I can reproduce it in 4.12.1, but not in 4.14.0.
It leaves the etime unset if a onevm delete is executed while the VM is in state shutdown_undeploy.
Even if the bug is not present in 4.14, we should update fsck to look for this inconsistency.