Envoy not exporting metrics with -admin-bind option enabled

[pfridm01]

When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.

Overview of the Issue

We have two Mesh services running on the same VM. I run envoy proxy for each service.
consul connect envoy -sidecar-for producer
consul connect envoy -sidecar-for consumer -admin-bind $my_ip:19001

We are exporting L7 data to Prometheus from both, consumer and producer, proxies. However, the export does not occur when '-admin-bind' option is used (on either proxy).

curl http://127.0.0.1:9125/metrics
upstream connect error or disconnect/reset before headers. reset reason: connection failure

Reproduction Steps

Steps to reproduce this issue, eg:

1. Service configs:
   Producer
   ==================
   {"service":
   {"name": "producer",
   "token": "abc",
   "tags": ["ho","producer_ho"],
   "port": 5000,
   "connect": {
   "sidecar_service":{
   "proxy": {
   "config":{
   "envoy_prometheus_bind_addr": "0.0.0.0:9124"
   }
   }
   }
   },
   "check": {
   "args": ["curl", "localhost:5000"],
   "interval": "10s"
   }
   }
   }
   ==================
   Consumer
   ==================
   service {
   name = "consumer"
   port = 5001
   token = "abc"
   connect {
   sidecar_service {
   proxy {
   config = {
   envoy_prometheus_bind_addr = "0.0.0.0:9125"
   }
   upstreams = [
   {
   destination_name = "producer"
   local_bind_port = 5005
   }
   ]
   }
   }
   }
   check {
   "args" = ["curl", "localhost:5001"],
   "interval" = "10s"
   }
   }

==================

2. start envoy proxies with 'admin-bind' option enabled
   consul connect envoy -sidecar-for consumer -admin-bind <host_ip>:19001

3. curl http://127.0.0.1:9125/metrics
   upstream connect error or disconnect/reset before headers. reset reason: connection failure

4.start proxy without -admin-bind
consul connect envoy -sidecar-for consumer

5. curl http://127.0.0.1:9125/metrics

Consul info for both Client and Server

Client info

output from client 'consul info' command here

Server info

output from server 'consul info' command here

consul info
agent:
check_monitors = 2
check_ttls = 0
checks = 6
services = 4
build:
prerelease =
revision = 2cf0a3c
version = 1.7.1
consul:
acl = enabled
known_servers = 2
server = false
runtime:
arch = amd64
cpu_count = 2
goroutines = 118
max_procs = 2
os = linux
version = go1.13.7
serf_lan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 16
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 331
members = 4
query_queue = 0
query_time = 1

Operating system and Environment details

Centos 7 VM
envoy --version

envoy version: b67c14052c49890a7e3afe614d50979c346c024b/1.13.1/clean-getenvoy-95766ea-envoy/RELEASE/BoringSSL

[apollo13]

I think this can be closed since #10747 fixes this.

[blake]

@apollo13 Yup, I agree this can be closed. It's the same issue as #10747 which was fixed by PR #10757.