Comment 4 for bug 1311755

<sjmc7> oo, this was me
<sjmc7> we absolutely need to make sure the engine can report errors back to the API
<tnurlygayanov> yes, it is important
<sjmc7> especially since at the moment, the heat and murano records can be inconsistent
-*- ruhe rised importance to high
<sergmelikyan> I am not sure that we will fix this during juno-1. We have only 10 days left
<sjmc7> we need to at least have a good idea of how to handle it
<slagun> This was fixed. At least partially. If unhandled exception occurs during deployment API receives notification
<sjmc7> i.e. through the RPC path
<sergmelikyan> slagun, yeah, it is mentioned in comments to the issue. We need to redesign a little bit this part of interaction between API and Engine
<sergmelikyan> slagun, how do you think - you can fix this during juno-1?
<tnurlygayanov> slagun, could you please write the comments to this bug about this fix and how we can implement this is in future?
<sergmelikyan> as part of debuggability initiative?
<slagun> What exactly is left to do in that bug?
<tnurlygayanov> slagun looks like we don't know
<tnurlygayanov> and we should perform some investigation on this
<sergmelikyan> Add error state for environment? And rewrite part of the code that is responsible for sending notifications in case of exception.
<slagun> Me either. Need to think on that
<ruhe> slagun: will you please take an AI to work on this bug to figure out next steps?
<sergmelikyan> slagun, https://github.com/stackforge/murano/blob/master/murano/common/engine.py#L73
<tnurlygayanov> so, ok, I will add the comments to the description of this issue