I can't really ACK, this - as I said in irc, db-omatic doesnt do the right thing here. If I shut down a vm, it (db-omatic) says it is shutting down the vm (setting state) and clearing attributes. Then it sets the vm state back to running. Perhaps this is unrelated, but it does not work right as is.<br>
<br><div class="gmail_quote">On Fri, May 29, 2009 at 2:43 PM, Ian Main <span dir="ltr"><<a href="mailto:imain@redhat.com">imain@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This patch changes taskomatic so it only sets the VM to shutdown if<br>
the undefine succeeds. Otherwise it's possible a shutdown event could<br>
not succeed, or take a while as it often does, giving confusing<br>
messages to the user. Basically we're just letting dbomatic handle<br>
it now.<br>
<br>
Signed-off-by: Ian Main <<a href="mailto:imain@redhat.com">imain@redhat.com</a>><br>
---<br>
src/task-omatic/taskomatic.rb | 1 -<br>
1 files changed, 0 insertions(+), 1 deletions(-)<br>
<br>
diff --git a/src/task-omatic/taskomatic.rb b/src/task-omatic/taskomatic.rb<br>
index 11d13cb..5393c29 100755<br>
--- a/src/task-omatic/taskomatic.rb<br>
+++ b/src/task-omatic/taskomatic.rb<br>
@@ -286,7 +286,6 @@ class TaskOmatic<br>
result = vm.undefine<br>
if result.status == 0<br>
@<a href="http://logger.info" target="_blank">logger.info</a> "Deleted VM #{db_vm.description}."<br>
- set_vm_shut_down(db_vm)<br>
teardown_storage_pools(node)<br>
end<br>
return<br>
<font color="#888888">--<br>
1.6.0.6<br>
<br>
_______________________________________________<br>
Ovirt-devel mailing list<br>
<a href="mailto:Ovirt-devel@redhat.com">Ovirt-devel@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/ovirt-devel" target="_blank">https://www.redhat.com/mailman/listinfo/ovirt-devel</a><br>
</font></blockquote></div><br>