HAProxy will refuse to start if it cannot resolve any name.
HAProxy will refuse to start if it cannot resolve any name.

In a context in which cloud-init could be updating the hostnames after
machines are continuing with the update orchestration, we could be
writing one thing to `/etc/hosts` and another one in the `haproxy`
configuration, refusing this one to start because it cannot resolve
the new name.

This easily fixable in a newer HAProxy version by using the `init-addr`
configuration, so HAProxy won't refuse to start if it cannot resolve
any backend -- it will just ignore it --.

For now, let's make the temporal window as small as possible, making
the `haproxy` init.sls depend on the `etc-hosts` SLS, as it's *so*
dependant on it.

However, this is not in any way an ideal fix; rather a way to make
this problematic window as small as possible.

Fixes: bsc#1097478

ereslibre/salt,kubic-project/salt,ereslibre/salt,ereslibre/salt,kubic-project/salt,kubic-project/salt