murano-agent dead-lock on wrong execution-plan
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Confirmed
|
Medium
|
Unassigned |
Bug Description
During loop on process execution plan, there is no try/catch to protect the code sequence. So if there is an exception raised from get_execution_
def _loop_func(self, msg_iterator):
result, timestamp = self._queue.
if result is not None:
if self._send_
return
plan = self._queue.
if plan is not None:
return
tags: | added: agent |
tags: | added: low-hanging-fruit |
Changed in murano: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → ocata-1 |
Changed in murano: | |
assignee: | nobody → Jaewoo Park (aselius) |
Changed in murano: | |
assignee: | Jaewoo Park (aselius) → nobody |
Changed in murano: | |
milestone: | 3.1.0 → pike-2 |
Changed in murano: | |
milestone: | pike-2 → pike-rc1 |
Could you please provide more information on your use cases? In normal usage you cannot get json decoding exceptions for jsons that were produced by the very same application. And if the corrupted json was put there by someone else hanging until it fixed back by the user might be a reasonable behavior