When ElasticSearch is down, ArticleBundle doesn't recognize it and display a readable error.

[Swader]

Q	A
Bug?	Yes
New Feature?	no
SuluArticleBundle Version	Any working ArticleBundle / Sulu combo

Actual Behavior

When ElasticSearch is down, the Articles screen in the adminUI dies with a perpetual loader displayed. It doesn't read the 500 error message provided by the app.

Expected Behavior

There should be a flashing error message saying something like "No ES nodes available on the server".

Steps to Reproduce

Install Sulu and ArticleBundle. Kill ES. Open Articles UI in Admin UI.

Possible Solutions

Read the error message (it's very well structured) and produce a simple warning div with its main message flashed. Image below.