Comment 0 for bug 1712127

I'm relating my applications to haproxy:website. haproxy seems to be giving an address that is unresolvable by consumers.

This might be exacerbated by the fact that the unit provisioned by Juju (2.x, openstack provider) doesn't seem to resolve its own name:

(mojo-stg-omnibus)stg-omnibus@wendigo:~$ juju ssh omnibus-internal/0
Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-92-generic x86_64)

 * Documentation: https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support: https://ubuntu.com/advantage

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

2 packages can be updated.
0 updates are security updates.

Last login: Mon Aug 21 17:19:26 2017 from 91.189.90.53
ubuntu@juju-5d3328-stg-omnibus-12:~$ hostname
juju-5d3328-stg-omnibus-12
ubuntu@juju-5d3328-stg-omnibus-12:~$ ping juju-5d3328-stg-omnibus-12
ping: unknown host juju-5d3328-stg-omnibus-12

The haproxy charm should provide a resolve-able address in the relation, such as hookenv.unit_public_ip().