haproxy 1.8.4 has hit the bionic archive. Since it's now a sync, there
is no mention of this bug in its changelog, so I'm closing this bug
manually.
** Changed in: haproxy (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of
Other tests I just finished:
- deploy large app with charms, haproxy on bionic. Verify app works. Upgrade
haproxy to 1.8.4. app still works. Add new backend to app, works.
- upgrade xenial to bionic, with the ppa for haproxy 1.8.4 enabled. Tested
simple config (haproxy as fe, one apache as
I performed the following tests so far:
- used a charm bundle to deploy a complex application that uses haproxy as the
frontend, with and without ssl (landscape-server). Added backends after the
deployment as well. Worked as expected
- tried reload while there were ongoing live connections to
It looks like this can become a sync indeed. I'm testing a package I
built on this ppa:
https://launchpad.net/~ahasenack/+archive/ubuntu/haproxy-18-merge-1748210/+packages
It still has the "ubuntu" suffix, just because that's what I arrived at
after doing the merge, but it has no delta.
--
You
** Changed in: haproxy (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: haproxy (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
