Bug 1738520
| Summary: | Live storage migration fails of a read only disk fails causing the VM not to be powered down | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Evelina Shames <eshames> | ||||
| Component: | BLL.Storage | Assignee: | Benny Zlotnik <bzlotnik> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Avihai <aefrat> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.3.6.1 | CC: | bugs, lsvaty, michal.skrivanek, pkrempa, tnisan | ||||
| Target Milestone: | ovirt-4.4.1 | Keywords: | Automation, Regression | ||||
| Target Release: | --- | Flags: | pm-rhel:
ovirt-4.4+
pm-rhel: blocker? |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-04-02 13:22:01 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Hi Evelina, What does "100% (automation TC)" means ? Does this issue reproduce all the time ? 100%? This looks like a pretty basic flow, does this reproduce manually? Also was this started occurring in 4.3.6 ? If so please add "regression" to the Keywords and set the severity to high. Yes, it reproduces all the time, manually as well. I found this issue when running one of our TCs, that's why I have mentioned "automation TC". I saw it in 4.3.6 EA, but I tried to run this TC on 4.3.5.4-0.1 env and it reproduced. Additional info: * After LSM fails, when trying to power off the VM it stucks in 'powering down' state and it is impossible to run other VMs on its host. * LSM of RW disk works for me, the issue is only for RO disk. This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. Evelina can we check this issue is still present? Currently targeting to 4.4.0, as a Regression flow that should be fixed in Beta. If not reproducible, please close. Isn't this a duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=1759933#c25 At any rate yes, snapshot of read-only disk was forbidden for the better or worse. We can either relax that if the remote file is provided or alternatively allow block-copy of readonly disks which should be possible with -blockdev now and doesn't then require any merging etc. yeah it absolutely is. thank you! *** This bug has been marked as a duplicate of bug 1759933 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Created attachment 1601323 [details] logs Description of problem: LSM's diskReplicateFinish failed with TimeoutError: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainBlockJobAbort) VM becomes Not Responding Version-Release number of selected component (if applicable): ovirt-engine-4.3.5.4-0.1 vdsm-4.30.24-2.el7ev.x86_64 How reproducible: 100% (automation TC) Steps to Reproduce: 1) 2 iscsi storage domains 2) VM with OS 3) Attach read-only disk (on first iscsi storage domain) to the VM 4) Activate the disk 5) Try to move the disk (LSM) to the second storage domain Actual results: LSM should succeed Expected results: LSM fails Additional info: logs are attached (ovirt-engine-4.3.6-0.1, vdsm-4.30.25-1.el7ev.x86_64, libvirt-4.5.0-23.el7.x86_64)