Bug 1778032 - [RFE] Allow importing VM disks only without the VM itself.
Summary: [RFE] Allow importing VM disks only without the VM itself.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.3.6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Mark Kemel
QA Contact: Avihai
URL:
Whiteboard:
: 1881457 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-29 04:49 UTC by Germano Veit Michel
Modified: 2023-03-24 16:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-19 08:23:39 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Germano Veit Michel 2019-11-29 04:49:25 UTC
Description of problem:

It is possible for the user to put himself in a difficult situation by doing the following:

1. Create a VM
2. Create disk A for the VM on SD A
3. Create disk B for the VM on SD B
4. Detach SD B
   * VM still exists, but only has disk A
5. Attach SD B again
   * In SD B -> VM Import, the VM shows up, cut cannot import as VM exists
   * In SD B -> Disk Import, Disk B is not there

So:
-> Cannot import the VM, because the VM already exists
-> Cannot import only the missing disk, because its not in the Disk Import Tab

There are ways to get out of it:
a) Edit the DB to remove the link between the VM and the Disk on SD B, so that the disk B shows up in the Disk Import Tab
b) Delete the VM while keeping the disk A, Import the VM from SD B while allowing Partial, then re-attach the existing disk A.

Could you please evaluate if this could be made more user friendly?

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.6.7-1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a VM
2. Create disk A for the VM on SD A
3. Create disk B for the VM on SD B
4. Detach SD B
5. Attach SD B
6. Try to get the VM back with its 2 disks

Expected results:
Its relatively easy to get the VM back, but its not user friendly

Comment 2 Arik 2021-01-13 16:12:43 UTC
This one is about importing from a storage domain which is a feature owned by the storage team.
FWIW, getting into this situation of having a VM that doesn't have all its disks available due to the fact a storage domain is detached is problematic.

Comment 3 Eyal Shenitzky 2021-08-29 09:16:41 UTC
This is done by design and not going to be changed.

What I do suggest is to allow import VM disks only without the VM itself so the user will not need to remove the original VM from his environment.

Comment 4 Eyal Shenitzky 2021-08-29 10:21:04 UTC
*** Bug 1881457 has been marked as a duplicate of this bug. ***

Comment 7 Sandro Bonazzola 2022-03-29 16:16:40 UTC
We are past 4.5.0 feature freeze, please re-target.

Comment 8 Michal Skrivanek 2022-04-20 11:18:32 UTC
unfortunately this didn't make it for RHV 4.4SP1, moving back to prioritization queue

Comment 9 Michal Skrivanek 2022-05-19 08:23:39 UTC
Unfortunately this request was not prioritized and didn't make it into RHV 4.4SP1. There are no further major RHV releases planned to implement this in(see https://access.redhat.com/support/policy/updates/rhev for RHV lifecycle information)


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