The services randomly do not register correctly when starting blue locally

When starting the blue reference distribution, some of the services will randomly register themselves incorrectly. This can be verified using the Consul UI (started with the blue distribution under localhost:8500) - most of the services will be registered at unique IP, but some of them (random ones) will be registered at localhost. The services that get registered on localhost will not be available and any attempt to use an endpoint from that service fails. This problem doesn't seem to affect test/uat deployment servers for some reason, but it happens quite often on local dev machines.

Acceptance criteria

• When starting blue, the services get properly registered (none of them on localhost, verified via Consul UI)

• All services are available after starting blue

• Verify the above with the test server and especially local dev machines