It seems the JS for this section is prioritizing the fact that the node was going to be failed over above the fact that the node is no longer available.
I'm not sure what the server-side logic relationship is in this situation, but hopefully it's just a matter of re-prioritizing some conditions in the UI JS.
|Assignee||Aleksey Kondratenko [ alkondratenko ]||Pavel Blagodov [ pavel ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|