Add loging for sending an action to executor

Closes-Bug: #1805579
Change-Id: I4dc2b1e059d66d16725417ea5aa27b978e2163f0
This commit is contained in:
Renat Akhmerov 2018-11-28 13:49:12 +07:00
parent c4ccb70feb
commit 0fb96bbd2b
3 changed files with 23 additions and 2 deletions

View File

@ -87,7 +87,7 @@ class ExecutorServer(service_base.MistralService):
:return: Action result.
"""
LOG.info(
LOG.debug(
"Received RPC request 'run_action'[action_ex_id=%s, "
"action_cls_str=%s, action_cls_attrs=%s, params=%s, "
"timeout=%s]",
@ -103,7 +103,7 @@ class ExecutorServer(service_base.MistralService):
try:
self._aer.add_action_ex_id(action_ex_id)
return self.executor.run_action(
res = self.executor.run_action(
action_ex_id,
action_cls_str,
action_cls_attrs,
@ -113,6 +113,15 @@ class ExecutorServer(service_base.MistralService):
redelivered,
timeout=timeout
)
LOG.debug(
"Sending action result to engine"
" [action_ex_id=%s, action_cls=%s]",
action_ex_id,
action_cls_str
)
return res
finally:
self._aer.remove_action_ex_id(action_ex_id)

View File

@ -381,6 +381,11 @@ class ExecutorClient(exe.Executor):
rpc_client_method = (self._client.async_call
if async_ else self._client.sync_call)
LOG.debug(
"Sending an action to executor [action_ex_id=%s, action_cls=%s]",
action_ex_id, action_cls_str
)
return rpc_client_method(auth_ctx.ctx(), 'run_action', **rpc_kwargs)

View File

@ -0,0 +1,7 @@
---
fixes:
- |
Mistral doesn't log enough info about sending actions to executor and
receiving them on the executor side. It makes it hard to debug
situations when an action got stuck in RUNNING state. It has now been
fixed by adding additional log statements.