I ran into the same issue when importing VMs into oVirt 3.2, assigning them permissions to a user such as admin would allow them to survive the reboot and not disappear. In 3.3 that does not seem to be the case. I opened a BZ but I think it got closed.

Just for reference how'd you empty the async_tasks?

Andrew.

On Tue, Aug 27, 2013 at 10:44 PM, Frank Wall <fw@moov.de> wrote:

Hi Laszlo,

On 27.08.2013 14:24, Laszlo Hornyak wrote:

If I understand correctly, this is what happens to your installation,
the AddVmFromTemplate command goes to fail and engine tries to
compensate, and upon successful compensation you get VM records
removed from DB and storage cleaned up.

just to be sure, please note, that the task actually completed successfully from my point of view. The new VM (direved from the template clone task) is fully usable and on the webadmin the task is shown as "completed".

So maybe at some point in time the engine does get the job status wrong and the problem begins...

I need to look into this but I think it should be safe to remove this
record while the engine is down. Make sure to make a backup if you
try!

OK, I did the following test:

- created a new VM from my custom template (with cloned Disk)
- waited for the job to complete
- manually deleted the related DB entry from the table "async_tasks"
- set host/node to maintenance
- rebootet engine

Result: The VM did NOT disappear! :-)

I think somehow ovirt-engine does get the results of the job wrong, thus it does not recognize that the job completed *successfully* and does a retry after reboot (which fails horribly and leads to disappearing VMs).

Thanks
- Frank

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users