Feature:
The administrator will see a detailed report when a VM was not started for scheduling reasons.
The report contains the filter that was responsible for removing each candidate host from the candidate list.
Reason:
Our users were confused when a complicated situation in the cluster prevented them from starting a VM.
Result (if any):
engine.log contains detailed information and the popup error dialog contains the detailed report as well.
Created attachment 791292[details]
screen
Description of problem:
Provide more informative error message and logs when there is no host which vm can run on.
Version-Release number of selected component (if applicable):
is11
How reproducible:
always
Steps to Reproduce:
1. Create new cluster policy and select only pin_to_host filter.
2. Assign this new cluster policy to your cluster with at least two hosts.
3. Create vm which is pinned to host1 and select 'do not allow migration'
4. Switch host1 to maintanence and host2 up.
5. Run vm.
Actual results:
popup 'Error while executing action:'
Expected results:
popup 'Error while executing action: There is no host suitable to run vm'
Additional info:
engine.log
2013-08-28 12:09:50,063 INFO [org.ovirt.engine.core.bll.RunVmCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] Lock Acquired to object EngineLock [exclusiveLocks= key: 5aa817b9-ea94-4a88-a85c-5cc5cc9b3e99 value: VM
, sharedLocks= ]
2013-08-28 12:09:50,086 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] START, IsVmDuringInitiatingVDSCommand( vmId = 5aa817b9-ea94-4a88-a85c-5cc5cc9b3e99), log id: 5641ed98
2013-08-28 12:09:50,086 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 5641ed98
2013-08-28 12:09:50,090 WARN [org.ovirt.engine.core.bll.RunVmCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] CanDoAction of action RunVm failed. Reasons:VAR__ACTION__RUN,VAR__TYPE__VM
2013-08-28 12:09:50,090 INFO [org.ovirt.engine.core.bll.RunVmCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] Lock freed to object EngineLock [exclusiveLocks= key: 5aa817b9-ea94-4a88-a85c-5cc5cc9b3e99 value: VM
, sharedLocks= ]
Created attachment 791292 [details] screen Description of problem: Provide more informative error message and logs when there is no host which vm can run on. Version-Release number of selected component (if applicable): is11 How reproducible: always Steps to Reproduce: 1. Create new cluster policy and select only pin_to_host filter. 2. Assign this new cluster policy to your cluster with at least two hosts. 3. Create vm which is pinned to host1 and select 'do not allow migration' 4. Switch host1 to maintanence and host2 up. 5. Run vm. Actual results: popup 'Error while executing action:' Expected results: popup 'Error while executing action: There is no host suitable to run vm' Additional info: engine.log 2013-08-28 12:09:50,063 INFO [org.ovirt.engine.core.bll.RunVmCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] Lock Acquired to object EngineLock [exclusiveLocks= key: 5aa817b9-ea94-4a88-a85c-5cc5cc9b3e99 value: VM , sharedLocks= ] 2013-08-28 12:09:50,086 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] START, IsVmDuringInitiatingVDSCommand( vmId = 5aa817b9-ea94-4a88-a85c-5cc5cc9b3e99), log id: 5641ed98 2013-08-28 12:09:50,086 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 5641ed98 2013-08-28 12:09:50,090 WARN [org.ovirt.engine.core.bll.RunVmCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] CanDoAction of action RunVm failed. Reasons:VAR__ACTION__RUN,VAR__TYPE__VM 2013-08-28 12:09:50,090 INFO [org.ovirt.engine.core.bll.RunVmCommand] (ajp-/127.0.0.1:8702-10) [2fc2bb36] Lock freed to object EngineLock [exclusiveLocks= key: 5aa817b9-ea94-4a88-a85c-5cc5cc9b3e99 value: VM , sharedLocks= ]