In Eureka First Bootstrap mode, config data wouldn't load if a client starts on a random port number

In Eureka First mode, if client starts on a random port (--server.port=0), the client code will ignore the Eureka setup and always try to load config data from default location (localhost:8888). In my case, I have config server runs on 8810, and the client bootstrap as,

spring.application.name=test-server
server.port=0

spring.cloud.config.discovery.enabled=true
spring.cloud.config.discovery.serviceId=config-server

eureka.client.serviceUrl.defaultZone=http://localhost:8020/eureka/
eureka.instance.metadataMap.instanceId=${spring.application.name}:${spring.application.instance_id:${random.value}}

Here is the error when my client bootup,

2015-02-26 14:11:30.320 ERROR 21609 --- [           main] c.c.c.ConfigServicePropertySourceLocator : Could not locate PropertySource: I/O error on GET request for "http://localhost:8888/test-server/default/master":Connection refused; nested exception is java.net.ConnectException: Connection refused

Start with ConfigServicePropertySourceLocator and the bootstrap handling for Eureka First mode, using the configuration shown in the issue with a random server port and a config server on port 8810. Reproduce the failed lookup and trace why it falls back to localhost:8888; done means config data is loaded through Eureka service discovery instead.