Bug 1380483
Summary: | [Docs] - Attempting to correlate between an engine disk to the disk within a vm it should be done using the device serial | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Bimal Chollera <bcholler> |
Component: | Documentation | Assignee: | rhev-docs <rhev-docs> |
Status: | CLOSED DUPLICATE | QA Contact: | rhev-docs <rhev-docs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0.3 | CC: | aaviram, ahadas, amureini, bcholler, eheftman, laravot, lbopf, lsurette, mavital, rbalakri, Rhev-m-bugs, srevivo, tnisan, tspeetje, ykaul, ylavi |
Target Milestone: | ovirt-4.1.3 | ||
Target Release: | --- | ||
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: | 2017-08-08 07:38:57 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bimal Chollera
2016-09-29 17:55:38 UTC
Amit/Liron - I have a vague recollection you both handled issues around this area. Could you weigh in please? (In reply to Allon Mureinik from comment #1) > Amit/Liron - I have a vague recollection you both handled issues around this > area. Could you weigh in please? Mmmm I don't have anything helpful to contribute here without having a thorough look- though I was dealing some issues in VDSM's part regarding the device's serial tag. Let me know if you need me to have a deeper look. Hi Bimbal, Currently when running a VM we pass the defined devices (including the disks obviously), the assigned device names/addresses are out of oVirt scope. The assigned addresses/device name are retrieved by oVirt. The assigned addresses are used for the next runs of the VM so the same address will be used for the same device - the fact that currently the order affect the assigned addresses/device names is an implementation detail which we cannot enforce. oVirt supports reporting of the device name given for each disk (see https://www.ovirt.org/develop/release-management/features/engine/reportguestdiskslogicaldevicename/ ) - is that sufficient for the customer needs? thanks, Liron. Arik, I recall you changed the mechanism of the disk order, is it related to this bug? (In reply to Tal Nisan from comment #10) > Arik, I recall you changed the mechanism of the disk order, is it related to > this bug? I don't remember doing such a change. (In reply to Arik from comment #11) > I don't remember doing such a change. If you meant the change that eliminated the persistence of boot order on each device in the database then no, and it was not backported to 4.0.3. Moving out all non blocker\exceptions. This appears to be a duplicate of bug 1429751. If that is not the case, please reopen this bug. *** This bug has been marked as a duplicate of bug 1429751 *** |