** Changed in: haproxy (Ubuntu Disco)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1846714
Title:
Merge "BUG/MEDIUM: server:
FTR: I couldn't find an upstream bug for this.
** Changed in: haproxy (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: haproxy (Ubuntu Disco)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which
Hello Malte,
I tried to reproduce the behavior you describe using the haproxy.cfg you
provided, but without success. I have some questions that may help us
getting in sync with what are observing.
1. Your haproxy.cfg doesn't work in Bionic and Eoan because haproxy complains
that the following
Set up HAProxy with the attached configuration. The server-template
directive will generate 3 upstreams based on the DNS-answers for
letsencrypt.status.io. This is basic HAProxy DNS-service-discovery.
If you now check back with the stats socket or the webinterface, you
will notice that while the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Is there an upstream bug link for this issue please?
If any upstream bug does not provide this information already, please
could you provide exact steps to reproduce the problem and an
explanation of how it
Upstream 2.0 branch commit:
https://git.haproxy.org/?p=haproxy-2.0.git;a=commit;h=21944019cabcb46ceb95b7fd925528b9dace4e35
Looks like this was fixed before the release of the 2.0 series, so this
is Fix Released for the development release.
** Also affects: haproxy (Ubuntu Disco)
Importance:
6 matches
Mail list logo
