Description of problem: The fix for BZ #1135939 is local to addVmCommand, I have encountered same issue upon importing a VM: 2014-10-14 14:15:40,548 WARN [org.ovirt.engine.core.bll.ImportVmCommand] (ajp-/127.0.0.1:8702-1) [153b361b] CanDoAction of action ImportVm failed. Reasons:VAR__ACTION__IMPORT,VAR__TYPE__VM,BALLOON_REQUESTED_ON_NOT_SUPPORTED_ARCH,$clusterArch ppc64 2014-10-14 14:15:40,549 INFO [org.ovirt.engine.core.bll.ImportVmCommand] (ajp-/127.0.0.1:8702-1) [153b361b] Lock freed to object EngineLock [exclusiveLocks= key: ppc_MeM_64_Copy value: VM_NAME , sharedLocks= key: 1158224a-b7ea-4b96-b4b4-deebb68adf91 value: REMOTE_VM ] the operation is CDA blocked. Version-Release number of selected component (if applicable): av12 How reproducible: 100% Steps to Reproduce: 1.import VM from export domain Actual results: Expected results: Additional info:
Vitor, can you please check?
This bug only happens in 3.4.3, I have created a fix for it.
Ori, please confirm the engine version. Bug is filed with 3.5; but the bug is relevant only in 3.4.z
Michal - I reluctantly agree at this point. In theory, there should be no new VMs to import up front, but that can quickly change once people start using export domains. Please provide the Doc Text for release note on the impact of this at GA.
** engine version:3.4.3-1.2.el6ev **
verified in vt9
RHEV-M 3.5.0 has been released