Bug 1577060
Summary: | Live merge failed because HSM did not refresh the base volume after extension | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Germano Veit Michel <gveitmic> |
Component: | ovirt-engine | Assignee: | Ala Hino <ahino> |
Status: | CLOSED DUPLICATE | QA Contact: | Elad <ebenahar> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.5 | CC: | ahino, gveitmic, lsurette, rabraham, rbalakri, Rhev-m-bugs, srevivo, tnisan |
Target Milestone: | ovirt-4.2.4 | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-16 04:10:34 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: |
Description
Germano Veit Michel
2018-05-11 06:39:15 UTC
2018-05-09 07:19:46,592+12 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (pool-6-thread-2) [7eb16c83-2493-40a4-b158-694cdbc860e2] Running command: RemoveSnapshotSingleDiskLiveCommand internal: true. Entities affected : ID: 3c0e67db-ccee-4bdb-81a8-19d908e8f05d Type: Storage Extend (SPM) 2018-05-09 07:19:46,781+12 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ExtendImageSizeVDSCommand] (pool-6-thread-4) [7eb16c83-2493-40a4-b158-694cdbc860e2] START, ExtendImageSizeVDSCommand( ExtendImageSizeVDSCommandParameters:{runAsync='true', storagePoolId='9ede6309-174a-4dec-95ef-73ce342542b6', ignoreFailoverLimit='false'}), log id: 720acf8e Refresh (HSM) ??? Merge (HSM) 2018-05-09 07:19:55,087+12 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand] (pool-6-thread-5) [7eb16c83-2493-40a4-b158-694cdbc860e2] START, MergeVDSCommand(HostName = pxlswh01, MergeVDSCommandParameters:{runAsync='true', hostId='b76d1a36-3d4b-4fee-96dc-1f370acf0888', vmId='84d8465f-df72-4f80-a45c-8bee9feb66e2', storagePoolId='9ede6309-174a-4dec-95ef-73ce342542b6', storageDomainId='3c0e67db-ccee-4bdb-81a8-19d908e8f05d', imageGroupId='67d2cfd4-9792-4edb-af9b-ac7210318996', imageId='ab8a38c4-729f-4074-a600-84b96ce6ca7a', baseImageId='d487966c-78f6-41fc-8a51-affb14f6f1c8', topImageId='ab8a38c4-729f-4074-a600-84b96ce6ca7a', bandwidth='0'}), log id: 266af902 Ah, this is unfortunate ... This is a duplicate of bug 1232481 that was fixed in Vdsm 4.17.36 (version reported in the bug description is 4.17.35). There is a confusion between bug 1232481 and bug 1367281. However, the path fixing this issue in 3.6 is https://gerrit.ovirt.org/#/c/63634/ that is included in the following branches/tags: Branches: ovirt-3.6, ovirt-3.6-async Tags: v4.17.36, v4.17.37, v4.17.38, v4.17.39, v4.17.40, v4.17.41, v4.17.42, v4.17.43, v4.17.43.1, v4.17.44 Germano, Can you please confirm this? (In reply to Ala Hino from comment #5) > Ah, this is unfortunate ... > This is a duplicate of bug 1232481 that was fixed in Vdsm 4.17.36 (version > reported in the bug description is 4.17.35). > > There is a confusion between bug 1232481 and bug 1367281. > However, the path fixing this issue in 3.6 is > https://gerrit.ovirt.org/#/c/63634/ that is included in the following > branches/tags: > > Branches: ovirt-3.6, ovirt-3.6-async > > Tags: v4.17.36, v4.17.37, v4.17.38, v4.17.39, v4.17.40, v4.17.41, v4.17.42, > v4.17.43, v4.17.43.1, v4.17.44 > > > Germano, > > Can you please confirm this? Hi Ala, Ahhh. So it's not the engine that sends that RefreshVolume command to the host running the vm on this case? Because I looked at this: https://gerrit.ovirt.org/#/c/47671/ and it does look like the engine should send this the refresh command after an extension during live merge command, which was not sent in this case. So a 4.1 engine with a 3.6 vdsm the command is not sent and the user needs the patched vdsm. Is this correct? Hi Germano, Base volume refresh is done at vdsm side. The refresh in that patch is done **not** after extending the base volume, but rather it is done if the base volume is ILLEGAL. Not sure what this patch tried to target. The user does need to upgrade vdsm to get the fix. Hi Ala, Thanks for clarifying and sorry for the confusion. *** This bug has been marked as a duplicate of bug 1232481 *** This bug is DUP of Bug 1232481 which has qe_test_coverage+ BZ<2>Jira Resync |