Random port config makes management.context-path invalid

[Flamingo93]

Config random server port by

server:
  port: 0

Also, I want to customize the prefix for the management endpoints, so I config eureka management.context-path by

management:
  context-path: /manage
eureka:
  instance:
    metadata-map:
      management:
        context-path: ${management.context-path}

Then, I found that default statusPageUrl and healthCheckUrl from eureka won't work, retrun 404.
Default statusPageUrl is "host:port/info" and it don't work, but "host:port/manage/info" still work.

Checking the source code, I found that in spring-cloud-netflix-eureka-client DefaultManagementMetadataProvider class, it process random port by

    public ManagementMetadata get(EurekaInstanceConfigBean instance, int serverPort,
                                  String serverContextPath, String managementContextPath,
                                  Integer managementPort) {
        if (isRandom(managementPort)) {
            return null;
        }
        if (managementPort == null && isRandom(serverPort)) {
            return null;
        }
        String healthCheckUrl = getHealthCheckUrl(instance, serverPort, serverContextPath,
                managementContextPath, managementPort, false);
        String statusPageUrl = getStatusPageUrl(instance, serverPort, serverContextPath,
                managementContextPath, managementPort);

        ManagementMetadata metadata = new ManagementMetadata(healthCheckUrl, statusPageUrl, managementPort == null ? serverPort : managementPort);
        if(instance.isSecurePortEnabled()) {
            metadata.setSecureHealthCheckUrl(getHealthCheckUrl(instance, serverPort, serverContextPath,
                    managementContextPath, managementPort, true));
        }
        return metadata;
    }

It will return null metadata when config port random, so that make default statusPageUrl and healthCheckUrl invalid.
Is it intentional or a bug? If intentional, why? Thx.

[spencergibb]

Please reopen if you can describe the problem or create a sample that reproduces it

[Flamingo93]

I don't have right to reopen issue closed by repo collaborator.
@spencergibb

[ryanjbaxter]

Provide the information requested and we will repopen.

[Flamingo93]

I have update the information. Am I clear?
@spencergibb @ryanjbaxter

[ryanjbaxter]

This is a duplicate of #3098