[
https://issues.apache.org/jira/browse/CLOUDSTACK-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862039#comment-13862039
]
ASF subversion and git services commented on CLOUDSTACK-5725:
-------------------------------------------------------------
Commit ce7bc8fd902831ea75e192e84a55e7a8895df917 in branch refs/heads/4.3 from
[~kelveny]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ce7bc8f ]
CLOUDSTACK-5725: put origin flow context id into log4j context prefix to link
jobs with the orchestration work flow in logging
> VMSync: Management Server Logs do not have information pertaining to API Job
> to Work Job Relation
> -------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5725
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5725
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Reporter: Chandan Purushothama
> Assignee: Kelven Yang
> Fix For: 4.3.0
>
>
> Currently a VM related API Job is dependent on multiple work jobs for the API
> job completion. The logs do not have any information pertaining to the
> dependency of API and Work Job. This confuses the User to track the job on
> the management server logs.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
