Bug 1264643

Summary: Disk move/migrate dialogues inconsistent
Product: [oVirt] ovirt-engine Reporter: Markus Stockhausen <mst>
Component: Frontend.WebAdminAssignee: Daniel Erez <derez>
Status: CLOSED CURRENTRELEASE QA Contact: Elad <ebenahar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.4CC: amureini, bugs, derez, ebenahar, ecohen, gklein, lsurette, mgoldboi, rbalakri, tnisan, yeylon, ylavi
Target Milestone: ovirt-3.6.1Flags: ylavi: ovirt-3.6.z?
ylavi: ovirt-4.0.0?
ylavi: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+
Target Release: 3.6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-16 12:23:15 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 Markus Stockhausen 2015-09-19 18:46:34 UTC
Description of problem:

There exit 2 ways of migration VM disk images between storage domains. They behave differently if executed for a disk of a running VM.


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

Ovirt 3.5.4

How reproducible:

100%

Steps to Reproduce:
1. Panel VM -> choose (running) VM -> Disks -> move disk 
1. Result: Panel gives warning about running VM

2. Panel disks -> choose disk of (running) VM -> move disk
2. Result: Panel gives NO warnung about running VM

Expected results:

Dialogues should behave the same.

Comment 1 Elad 2015-12-09 10:00:04 UTC
'Move' dialogue behaves the same for a running VM from the Disks main tab and from the Disks sub tab for the VM. In both dialogues the following warning is shown:

" Moving the following disk(s) while the VM is running: vm-1_Disk1 "


Verified using:
rhevm-3.6.1.1-0.1.el6.noarch
rhevm-webadmin-portal-3.6.1.1-0.1.el6.noarch

Comment 2 Sandro Bonazzola 2015-12-16 12:23:15 UTC
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.