Created attachment 871254 [details] engine.log and screenshots Description of problem: Storage domains from different types (file/block) are presented in 'Move' disks dialog under 'Disks' main tab in UI for live storage migration. Live storage migration for disks movement between different storage domains types (file/block) is not supported and is blocked in 'Move' dialog from 'Disks' sub-tab under 'Virtual machines' main tab. Version-Release number of selected component (if applicable): rhevm-3.4.0-0.3.master.el6ev.noarch How reproducible: Always Steps to Reproduce: On a shared DC with 2 storage domains from different types (file and block) 1. Create a VM with disk attached located on block domain 2. Start the VM, wait for it to become 'Up' 3. Under 'Disks' main tab --> 'Move' Actual results: File domains are presented under target domains list that are possible for a disk which is located on a block domain to be live migrated to (the same case for moving from file to block). When approving live migration from block to file, an error message is thrown and we're getting this CanDoAction failure message: 2014-03-06 10:02:54,967 WARN [org.ovirt.engine.core.bll.lsm.LiveMigrateVmDisksCommand] (ajp-/127.0.0.1:8702-9) [1e7d74a2] CanDoAction of action LiveMigrateVmDisks failed. Reasons:VAR__ACTION__MOVE,VAR__TYPE__VM_D ISK,ACTION_TYPE_FAILED_DESTINATION_AND_SOURCE_STORAGE_SUB_TYPES_DIFFERENT For doing the same action only from 'Disks' sub-tab under 'Virtual-machines' main tab, different domains type are filtered by file/block, so for live migration for disks which are located on block domains, file domains will not be presented under target domains list. Expected results: Target domains should be filtered by file/block also for live storage migration from 'Disks' main tab as it is for 'Disks' sub tab under 'Virtual-machines' main tab. Additional info: engine.log and screenshots
Tal, as long as we don't support LSM between subtypes, this needs to be filtered out. Also, please work with the docs team to provide a release-note (or whatever Jodi thinks is an appropriate way to document this).
verified using av5
Closing as part of 3.4.0