This cause a lot of headeache during the tests.

/reviewed-on !48

on generated supervisord config

If a promise anomaly timeout or return no message, we return error if
the problem is happening for a second time after a second run or if there was already an error.
This will reduce temporary failure.

On a setup for private cloud (internal master), reguralisation requests are not relevant and risky as alarms may trigger removal of instances due unpaid invoices.

This was done by Sven Franck.

Old software releases may have one old frontend url which leads to no software, this change allows others masters keep their own frontend configuration with existing software releases.

if the message size is too big, the promise process can hang on queue.put and parent process will no be able to read the message.
This will finally result in a deadlock situation.

Since 65f73750 the URLs are cached, so
test was failing because they were not isolated.

/reviewed-on !45