Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1095240 - PRD35 - [RFE] Support logging of commands parameters
Summary: PRD35 - [RFE] Support logging of commands parameters
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.5.0
Assignee: Ravi Nori
QA Contact: Pavel Novotny
Whiteboard: infra
Depends On: 1108861
Blocks: rhev3.5beta 1156165
TreeView+ depends on / blocked
Reported: 2014-05-07 10:42 UTC by Ilanit Stein
Modified: 2016-02-10 19:11 UTC (History)
12 users (show)

Fixed In Version: ovirt-3.5.0-alpha2
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2015-02-11 18:01:24 UTC
oVirt Team: Infra
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0158 normal SHIPPED_LIVE Important: Red Hat Enterprise Virtualization Manager 3.5.0 2015-02-11 22:38:50 UTC
oVirt gerrit 27780 master MERGED engine : Support logging of commands parameters Never

Description Ilanit Stein 2014-05-07 10:42:12 UTC
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):

Comment 1 Omer Frenkel 2014-05-08 10:22:40 UTC
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

Comment 2 Pavel Novotny 2014-10-22 13:45:49 UTC
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-/ [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

Comment 4 errata-xmlrpc 2015-02-11 18:01:24 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.