Bug 1138129 - alias disk names should be persisted in the Description of their meta data in the Storage Domain
Summary: alias disk names should be persisted in the Description of their meta data in...
Keywords:
Status: CLOSED DUPLICATE of bug 1047623
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.5.0
Assignee: Maor
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-04 06:43 UTC by Maor
Modified: 2016-02-10 16:34 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-04 11:14:03 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Maor 2014-09-04 06:43:05 UTC
Description of problem:
Currently alias names of disks are not persisted in the Storage Domain, so registering disks, will not have alias names. The alias name should be persisted in the Description of the disk in the Storage Domain.

How reproducible:
100%

Steps to Reproduce:
1. Register a disk
2.
3.

Actual results:
The disk will not have the same alias as before

Expected results:
The former alias of the disk should be present

Additional info:

Comment 1 Allon Mureinik 2014-09-04 11:14:03 UTC

*** This bug has been marked as a duplicate of bug 1047623 ***

Comment 2 Marina Kalinin 2015-04-09 21:40:01 UTC
Together with this, we should consider persisting disk's interface.
Today, if a disk is originally defined as Virtio, once the domain is imported, the disk looses the definition and considered as IDE.

Comment 3 Allon Mureinik 2015-04-12 14:40:11 UTC
(In reply to Marina from comment #2)
> Together with this, we should consider persisting disk's interface.
> Today, if a disk is originally defined as Virtio, once the domain is
> imported, the disk looses the definition and considered as IDE.
The disk interface is not part of the disk, it's a property of the relationship between the disk and the VM, and should be saved in the OVF.
This should be fixed for 3.5.3 with bug 1197444 - if it is not, please open another bug with all the relevant details.


Note You need to log in before you can comment on or make changes to this bug.