Bug 1551934 - No source storage domain identified when trying to move a VM's disk from the problematic storage
Summary: No source storage domain identified when trying to move a VM's disk from the ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.2.3
: ---
Assignee: shani
QA Contact: Yosi Ben Shimon
URL:
Whiteboard:
: 1551935 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-06 08:50 UTC by Polina
Modified: 2018-05-10 06:31 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-10 06:31:26 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
image attached (210.70 KB, image/png)
2018-03-06 08:50 UTC, Polina
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 89494 0 master MERGED webadmin: Fix move disk dialog 2020-02-11 23:18:19 UTC
oVirt gerrit 89596 0 ovirt-engine-4.2 MERGED webadmin: Fix move disk dialog 2020-02-11 23:18:19 UTC

Description Polina 2018-03-06 08:50:27 UTC
Created attachment 1404666 [details]
image attached

Description of problem: while there is some problem with nfs (down or deleted nfs mount dir) try to move the VM's disk to another storage. It could not be performed.
The error appears in the window that doesn't explain the reason

Version-Release number of selected component (if applicable):
rhv-release-4.2.2-3-001.noarch

How reproducible:100%


Steps to Reproduce:
1.Remove nfs directory for the domain to the VM is associated
2.Enter VM /Disks/Move Disks


Actual results: Message in window - "The following disks cannot be moved: golden_mixed_virtio_template, hover over a specific target domain selection for more info"

Expected results: Message must explain the reason the disk could not be moved, say something about the source disk doesn't exist


Additional info: image attached

Comment 1 Tal Nisan 2018-03-06 09:03:29 UTC
*** Bug 1551935 has been marked as a duplicate of this bug. ***

Comment 2 Tal Nisan 2018-03-06 09:05:36 UTC
Hi Polina,
It's quite the actual underlying reason is quite hard to display as Engine doesn't necessarily know about it, we can perhaps add a message that it cannot be moved since the source storage domain is down, will that be OK?

Comment 3 Polina 2018-03-06 09:35:52 UTC
(In reply to Tal Nisan from comment #2)
> Hi Polina,
> It's quite the actual underlying reason is quite hard to display as Engine
> doesn't necessarily know about it, we can perhaps add a message that it
> cannot be moved since the source storage domain is down, will that be OK?

yes, I think the user should get a message saying about the problem with the source  SD

Comment 4 shani 2018-03-27 14:34:09 UTC
A new description of the problem:
(See original bug's attached image)

When trying to move a disk from a storage domain which is on maintenance / inactive, there's no identification for the disk's source sd and the sd's name doesn't appear at all.

Comment 5 Polina 2018-04-25 07:01:58 UTC
tested on rhv-release-4.2.3-2-001.noarch.
The reason for OM_QA -> ASSIGNED
Nothing changed in the behavior - the same message has bee brought upon trying to move the VM disk while its Storage Domain is Down or in Maintenance.

Comment 8 Yosi Ben Shimon 2018-05-02 12:04:10 UTC
Tested using ovirt-engine-4.2.3.3-0.1.el7.noarch

Actual result:
The error message is been displayed when hover the source SD indicating that the SD is not active.

While verifying this bug, I noticed that:
if the source SD is NFS/GlusterFS (active) and the disk is thin provisioned - the orange rectangle that previously displayed the message: "The following disks cannot be moved: test_vm_Disk1, hover over a specific domain for more info" is empty but still being displayed.
See https://bugzilla.redhat.com/show_bug.cgi?id=1573865

Comment 9 Sandro Bonazzola 2018-05-10 06:31:26 UTC
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


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