Rudder

Since correction of #1974, we now cleanly unregister the service when there is a bootstrap check that fail. There is one which check that ALL mandatory DIT entries are present, and so that rudder-init ran.

Actually, I removed one such entry and the service return a 503:

--2017-04-25 14:36:03--  http://localhost:8080/rudder
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2017-04-25 14:36:03 ERROR 503: Service Unavailable.

But in https://xxx.xxx.xxx.xxx/rudder/ I'm getting the "Rudder is currently loading, please wait..." infinite page. We should have an other one for 503.

Regarding the previous message, on Rudder 3.1, when loading we have the following return:

--2017-04-25 15:05:35--  http://localhost:8080/rudder
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused.

When Rudder is loading, jetty does not answer, and apache returns a 503 too.

We can at least modify the "loading" message to include a reminder about rudder-init.