Red Hat Bugzilla – Bug 1095240
PRD35 - [RFE] Support logging of commands parameters
Last modified: 2016-02-10 14:11:46 EST
Description of problem: engine.log is missing information on what lead to the decision that "cluster doesn't exist", though it does exist, reported in bug 1095223: "Import VM fail on 3.3 "Cluster doesn't exist", though it does exist." Version-Release number of selected component (if applicable): rhevm-3.5.0-0.1000.2890.efcac0a.master.el6ev.noarch
well the only missing information is what cluster did the user send in the parameters, as we know the error is that we couldn't find the cluster. im changing this bug to a feature request, to have an option to print command parameters (as sent from the user/caller). we have the same infrastructure for VDS commands (commands that are executed in the VDS broker, which responsible to vdsm communication). it would be greate to have the same mechanism in the BLL, for all commands. i wonder if by default printing should be in debug or info (as it is in VDS commands) example of printing of DestroyVDSCommand: 2014-02-25 09:59:03,402 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (org.ovirt.thread.pool-6-thread-47) [28e7666b] START, DestroyVDSCommand(HostName = duba, HostId = 9df66e59-dbec-4e4c-b002-a6090ce619f2, vmId=3b40b641-9e47-4511-9c11-189aab5534cb, force=false, secondsToWait=0, gracefully=false), log id: ccb68b4
Verified in rhevm-3.5.0-0.15.beta.el6ev.noarch (vt6). In debug mode, BLL commands are printed with all arguments dumped. Example of import VM action in engine.log: 2014-10-22 15:31:02,949 INFO [org.ovirt.engine.core.bll.ImportVmCommand] (ajp-/127.0.0.1:8702-8) [5fd5f669] Running command: ImportVmCommand(Vm = VM [F19], VdsGroupId = 00000001-0001-0001-0001-0000000001f0, DiskMap = null, SourceDomainId = 38c0db4a-cfd7-4ef9-b8ed-6942ae42841b, DestDomainId = 6f60d892-3ef7-459d-9804-b4c8765c565a, CpuProfileId = null, ContainerId = 5d4f3c8a-7514-400d-a0f7-5c6c51178ba8, ForceOverride = false, ImportAsNewEntity = false, ImageToDestinationDomainMap = {d7c8d040-ad8b-44b6-ab03-2dd3cde4a03c=6f60d892-3ef7-459d-9804-b4c8765c565a}, ImagesExistOnTargetStorageDomain = false, CopyCollapse = false, TemplateMustExists = false, QuotaId = null, DiskProfileId = null, StorageDomainId = 6f60d892-3ef7-459d-9804-b4c8765c565a, IsInternal = false, StoragePoolId = 00000002-0002-0002-0002-00000000035b, ForceDelete = false, VdsId = null) internal: false. Entities affected : ID: 6f60d892-3ef7-459d-9804-b4c8765c565a Type: StorageAction group IMPORT_EXPORT_VM with role type ADMIN
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0158.html