Bug 1871792
Summary: | Importing VM using virt-v2v fails if service ovirt-engine restarted during AddDisk operation. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ameya Charekar <achareka> |
Component: | ovirt-engine | Assignee: | Liran Rotenberg <lrotenbe> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.3.10 | CC: | ahadas, emarcus, emesika, gveitmic, lrotenbe, mavital, michal.skrivanek, mperina |
Target Milestone: | ovirt-4.4.4 | ||
Target Release: | 4.4.4 | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.4.4 | Doc Type: | Bug Fix |
Doc Text: |
Previously, when importing a Virtual Machine using virt-v2v and the ovirt-engine service restarted, the import failed.
In this release, the import continues as long there is an async command running, allowing the import to complete successfully.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-13 16:01:37 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ameya Charekar
2020-08-24 10:21:36 UTC
If you restart during import, why is it surprising that it fails? Does it have any ill side effects or it can be just re-imported? Michal, it's not terribly bad, but I think the ask here is for compensation on engine-restart to not mess up the import. This is all async anyway and may take several hours to run. Perhaps it should survive a restart like some other operations do. Don't think there were side effects besides the obvious failure. Shouldn't we skip compensation on startup for commands set are set with compensationPhase = CommandCompensationPhase.END_COMMAND ? This bug has a low overall severity and passed automated regreession suite, it is not going to be further verified by QE. If you believe a special care is required feel free to re-open to ON_QA status Due to QE capacity we are not going to cover this issue in our automation |