Bug 1727871
Summary: | [V2V] VM migration fails when using slow NFS remote storage | ||
---|---|---|---|
Product: | Container Native Virtualization (CNV) | Reporter: | Igor Braginsky <ibragins> |
Component: | V2V | Assignee: | Tomáš Golembiovský <tgolembi> |
Status: | CLOSED WONTFIX | QA Contact: | Igor Braginsky <ibragins> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.0 | CC: | bthurber, cnv-qe-bugs, dagur, fdupont, fsimonce, mgoldboi, ncredi, rgarcia, sgordon, tgolembi, tjelinek |
Target Milestone: | --- | ||
Target Release: | 2.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kubevirt-v2v-conversion-container-v2.1.0-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-01-13 05:40:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Igor Braginsky
2019-07-08 12:04:43 UTC
The problem is the timeout (10 minutes) until which the conversion pod needs to prepare. On faster NFS it is able to do it, on slower not. was moved by mistake Close no, Retarget probably yes Restoring need info to tgolembi If you have a slower storage it certainly affects the VM performance but there is nothing which would timeout so in this sense it is v2v only issue. Targeting to 2.1 @Brett, I will validate if the env is functional, if not - I will need to build it. I can do that with no problem, it will just take some time I don't have environment where to test it, all my deployments are failing, or, even if deployment is successful, migration doesn't work due to V2V issues. Do you have any working environment where I can add NFS storage and try migration? From IMS point of view, we don't consider this BZ as a blocker. adding need info on QE (for tracking) (In reply to Fabien Dupont from comment #21) > From IMS point of view, we don't consider this BZ as a blocker. If everyone agrees, can anyone move this out of 2.1.0? (Either to 2.1.1 or 2.2) Thank you. (In reply to Federico Simoncelli from comment #23) > (In reply to Fabien Dupont from comment #21) > > From IMS point of view, we don't consider this BZ as a blocker. > > If everyone agrees, can anyone move this out of 2.1.0? (Either to 2.1.1 or > 2.2) > Thank you. Will make the call on this next week. Placing this back to ON_QA for additional testing with new conversion POD. please add fixed in version Closing as NFS isn't supported storage for CNV. |