charm not "processing" 2 or more haproxy frontends

Bug #1806962 reported by Junien F
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Docker Registry Charm
Triaged
Low
Kevin W Monroe

Bug Description

Hi,

I have deployed 2 docker-registry units fronted by 2 haproxy units. I see 2 small bugs :

1. status message for the docker-registries only mention the IP of the first haproxy unit :

 docker-registry/0* active idle 0 1.2.3.4 5000/tcp Listening on 1.2.3.5 (http, proxied).

2. the insecure-registries setting in /etc/docker/daemon.json only has the IP of the first haproxy unit :

$ sudo cat /etc/docker/daemon.json
{
  "insecure-registries" : [ "1.2.3.5" ]
}

Minor, but worth fixing. Thanks !

Changed in layer-docker-registry:
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Kevin W Monroe (kwmonroe)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.