Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1647082

Summary:	I can start a live storage migration of a disk from disks view but not from disks subview for a specific SD
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Simone Tiraboschi <stirabos>
Component:	ovirt-engine	Assignee:	Ahmad Khiet <akhiet>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.7	CC:	aperotti, gshereme, ratamir, Rhev-m-bugs, tnisan
Target Milestone:	ovirt-4.3.1	Keywords:	UserExperience
Target Release:	4.3.0
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:	2019-02-26 13:50:30 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 Simone Tiraboschi 2018-11-06 16:20:36 UTC

Description of problem:
In the disk view there is the "move" button to trigger a live storage migration but the same button is not visible navigating from a specific storage domain to the disks sub view.
See the attached screenshots.

Version-Release number of selected component (if applicable):
4.2.7

How reproducible:
100%

Steps to Reproduce:
1. Try to start a live storage migration from disk page
2. Try to start a live storage migration from sd_disk page
3.

Actual results:
in disks page we have the "move" button but we cannot see it in the disks subpage for a specific SD.

Expected results:
move button is available also in disks subpage for a specific SD.

Additional info:

Comment 3 Sandro Bonazzola 2019-01-28 09:40:35 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 5 Tal Nisan 2019-02-26 13:50:30 UTC


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