Spring Cloud Services instance getting deployed with internal domain

Products

• Support Only for Spring

Issue/Introduction

There are two domains set up in the p-spring-cloud-services space: apps.internal and <apps domain> (ie the default application domain). When trying to create a config-server service in any org, the config-server instance is getting deployed with the route having the domain apps.internal.

The default apps domain, <apps domain>, is expected to be assigned to the config-server service instance.

The following error might be seen when accessing the config-server instance with an internal route:

Caused by: org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://config-61d9e542-064e-4982-9194-3b2625afe704.apps.internal/audit-logging-listener-service/cloud,DR": config-61d9e542-064e-4982-9194-3b2625afe704.apps.internal; nested exception is java.net.UnknownHostException: config-61d9e542-064e-4982-9194-3b2625afe704.apps.internal

As described in this doc:
 

"If a developer pushes an app without specifying a domain, a route is created for it from the first shared domain created in the system."
 

So if the internal domain is the first one listed out with the "cf domains" command, config-server will by default use the internal domain for creating new service instances.

For example:

$ cf domains
Getting domains in org DR as admin...

name                      availability   internal   protocols
apps.internal             shared         true       http
cfapps.example.com        shared                    http

Resolution

The domain ordering can't be adjusted in Tanzu Application Services for VMs.

The Spring Cloud Services product team is working on a permanent fix.  Until a fix is delivered, users can work around the issue by setting <apps domain> (or any other expected domain) in the SCS tile setting page ("Ops Manager > SCS > settings > SCS service broker -> Service instances domain" ). Then Apply Changes. This will override the default behavior and force SCS to deploy using the selected domain.