This bug was fixed in the package haproxy - 1.8.8-1ubuntu0.4
---
haproxy (1.8.8-1ubuntu0.4) bionic; urgency=medium
* d/p/stksess-align.patch: Make sure stksess is properly aligned.
(LP: #1804069)
* d/t/control, d/t/proxy-localhost: simple DEP8 test to actually
generate
This bug was fixed in the package haproxy - 1.8.13-2ubuntu0.2
---
haproxy (1.8.13-2ubuntu0.2) cosmic; urgency=medium
* d/p/stksess-align.patch: Make sure stksess is properly aligned.
(LP: #1804069)
* d/t/control, d/t/proxy-localhost: simple DEP8 test to actually
generate
Bionic verification
arm system:
root@bionic-haproxy-1804069:~# uname -a
Linux bionic-haproxy-1804069 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29
16:32:18 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux
using affected package at first:
root@bionic-haproxy-1804069:~# apt-cache policy haproxy
haproxy:
Cosmic verification
Using arm64:
root@cosmic-haproxy-1804069:~# uname -a
Linux cosmic-haproxy-1804069 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29
16:32:18 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux
First, confirming the bug:
root@cosmic-haproxy-1804069:~# apt-cache policy haproxy
haproxy:
Ok, thanks for trying. I can complete the verification and will post
results later today.
--
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/1804069
Title:
haproxy fails on
Andreas,
As far as cosmic goes
* I have no actual ARM hardware
* The cosmic cloud image will not boot on the cloud provider I have an account
with
* I can boot the aarch64 bionic cloud image
* LXD will install
* Creating a cosmic LXD container fails because systemd-networkd will not start
You can boot some other release for the host and use a lxd container for
the cosmic test.
--
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/1804069
Title:
haproxy fails on
Andreas, Paul checked the bionic package so comment #10 should hopefully
be sufficient. I am currently unable to boot the cosmic cloud aarch64
cloud image so verifying that might take some more time.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team,
I repeated the above tests on Bionic on a Qualcomm Centriq processor
with the package
http://launchpadlibrarian.net/409244670/haproxy_1.8.8-1ubuntu0.4_arm64.deb
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in
Jonathan, could you please detail what exactly you tested, and with
which package version? The SRU team will appreciate that level of
detail, which gives more confidence in the update.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1804069
Title:
haproxy fails on arm64
Hello Jonathan, or anyone else affected,
Accepted haproxy into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/haproxy/1.8.13-2ubuntu0.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
haproxy as shipped with bionic and cosmic doesn't work on arm64
architectures, crashing the moment it serves a request.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing,
in an arm64 system:
sudo apt update
** Description changed:
[Impact]
haproxy as shipped with bionic and cosmic doesn't work on arm64
architectures, crashing the moment it serves a request.
[Test Case]
* install haproxy and apache in an up-to-date ubuntu release you are testing,
in an arm64 system:
sudo apt update
** Description changed:
[Impact]
-
- * An explanation of the effects of the bug on users and
-
- * justification for backporting the fix to the stable release.
-
- * In addition, it is helpful, but not required, to include an
- explanation of how the upload fixes this bug.
+ haproxy as
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/haproxy/+git/haproxy/+merge/362210
--
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/1804069
** Description changed:
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/haproxy/+git/haproxy/+merge/362209
--
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/1804069
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * An explanation of the effects of the bug on users and
- * justification for backporting the fix to the stable release.
+ * justification for backporting the fix to the stable release.
-
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test
Tests kicked off:
cosmic: https://bileto.ubuntu.com/#/ticket/3610
bionic: https://bileto.ubuntu.com/#/ticket/3611
Those tickets have links to respective ppa builds, if someone wants to
test early.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team,
Bug reproduced, and fix confirmed.
--
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/1804069
Title:
haproxy fails on arm64 due to alignment error
Status in haproxy package
** Changed in: haproxy (Ubuntu Bionic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: haproxy (Ubuntu Cosmic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: haproxy (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in:
This was fixed upstream in 1.8.15:
2018/12/13 : 1.8.15
- MINOR: threads: Make sure threads_sync_pipe is initialized before using
it.
...
- BUG/MEDIUM: Make sure stksess is properly aligned. <--
Marking main task as fix released, as disco has 1.8.17. But confirmed
for bionic and
** Tags added: bitesize server-next
** Also affects: haproxy (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: haproxy (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which
** Changed in: haproxy (Ubuntu)
Status: Incomplete => Triaged
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
Minimal config that duplicates this:
--
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
maxconn 4096
defaults
log global
option dontlognull
option redispatch
retries 3
timeout client 50s
Hi Karl,
I've asked the reporter of the original haproxy bug to help out with a
test case - I don't have access to an arm64 system.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
Hi Jonathan,
Thanks for reporting this bug! Can you put together a simple test case
that reproduces the bug so that I can verify bug and fix?
** Changed in: haproxy (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
High
29 matches
Mail list logo
