Oops, back pedalling on this:
doko: I'm taking advantage of you reintroducing python-mako (py2),
to build haproxy with it (not a runtime dep). Is that why you reintroduced it,
or are other packages needing it?
ahasenack, ginggs: I just removed python2-scipy, so it's not needed for
that anymore
python-marko (py2) was reinstated, using it.
** Changed in: haproxy (Ubuntu)
Status: New => In Progress
** Changed in: haproxy (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
--
You received
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1828228
Title:
corosync fails to start in unprivileged containers - autopkgtest
failure
St
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855568
Title:
pcs depends on python3-tornado (>= 6) but it won't be installed
Status in pcs pac
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to ocfs2-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1852122
Title:
ocfs2-tools is causing kernel panics in Ubuntu Focal
(Ubuntu-5.4.0-9.12)
** Also affects: pcs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pcs (Ubuntu)
Status: New => In Progress
** Changed in: pcs (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member o
Public bug reported:
haproxy runs debian/dconv/haproxy-dconv.py when building its
documentation. That script is py2, and requires python2 and python-
marko.
python-marko is gone and is an NBS currently. The src:marko package now
only builds the python3 version, so we need to convert haproxy-dconv
** Changed in: haproxy (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Description changed:
Upstream haproxy has the concept of an LTS release, and a stable (non-
LTS) release. Currently, these are (see table at
http://www.haproxy.org/):
stable: 2.1.x
sta
n/sid, we will merge it manually into ubuntu.
1. https://lists.ubuntu.com/archives/ubuntu-
devel/2019-December/040853.html
** Affects: haproxy (Ubuntu)
Importance: Medium
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Tags: ahasenack
--
You received thi
Reproduced. Left part shows the o2cb test being run, and right side is
dmesg. It's focal, not eoan as the screenshot says, it's because I had
to start with eoan and dist-upgrade to focal.
** Attachment added: "Screenshot from 2019-11-14 17-13-34.png"
https://bugs.launchpad.net/ubuntu/+source/o
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
** Changed in: haproxy (Ubuntu)
Status: Confirmed => Triaged
--
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.n
Good to know. I also couldn't reproduce it just by using those commands,
some more setting up is probably needed. If we get reproducible steps,
we might be able to identify the commit (or series of commits) that
fixed it after 1.1.14. I took a quick look at the ChangeLog file but
failed to spot any
** Changed in: haproxy (Ubuntu)
Status: Expired => New
--
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/1828496
Title:
service haproxy reload sometimes fails to pick
** Summary changed:
- defragfs.ocfs2 hangs (or takes too long) on arm64
+ defragfs.ocfs2 hangs (or takes too long) on arm64, ppc64el
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to ocfs2-tools in Ubuntu.
https://bugs.launchp
** Bug watch added: github.com/markfasheh/ocfs2-tools/issues #42
https://github.com/markfasheh/ocfs2-tools/issues/42
** Also affects: ocfs2-tools via
https://github.com/markfasheh/ocfs2-tools/issues/42
Importance: Unknown
Status: Unknown
--
You received this bug notification beca
Public bug reported:
The new defragfs.ocfs2 test added in the 1.8.6-1 version of the package
hangs (or takes too long) in our dep8 infrastructure.
I reproduced this on an arm64 VM. The command stays silent, and
consuming 99% of CPU. There is no I/O being done (checked with iostat
and iotop).
str
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1819074
Title:
Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-
sssd master has pcre2 support via
https://github.com/SSSD/sssd/pull/677#issuecomment-508238642
eoan is getting 2.2.0, which doesn't have that yet, but getting closer!
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy i
Going over the details from comment #7
This is the state before the reload:
ubuntu@foo:~$ ps auxfwww | grep haproxy
root 1346 0.0 0.0 4356 684 ?Ss May22 0:00
/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg -p
/run/haproxy.pid
haproxy 2210 0.0 0.2 42644 1
You are forcing the compatibility between sysv and systemd into a corner
here. I understand that your idea is to provide a simple case to
reproduce the bug, but let's step back for a second and look at this
statement:
"""
The initscript is used as a LSB RA for pacemaker deployments; this bug
effe
Do you have fully qualified hostnames in the haproxy config? Or a bare
name?
** Changed in: haproxy (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bug
Still in the queue.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1795420
Title:
Keepalived update from 1.2.19 to 1.2.24 breaks support for /dev/tcp
health check
S
** Changed in: keepalived (Ubuntu)
Assignee: Karl Stenerud (kstenerud) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1795420
Title:
Keepalived up
Note that there is a systemd wrapper process in xenial:
411 ?Ss 0:00 /usr/sbin/haproxy-systemd-wrapper -f
/etc/haproxy/haproxy.cfg -p /run/haproxy.pid
413 ?S 0:00 \_ /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p
/run/haproxy.pid -Ds
432 ?Ss 0:00
maybe disco will need a pcs with a +really version to go back to 0.9. I
think we will know more once we get pacemaker 2 into eoan.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.ne
Switching zsh back to incomplete, according to previous comment. Thanks
for noticing that.
** Changed in: zsh (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
h
Thanks for the update, I missed that comment (again). I guess it can be
moved back to "triaged" then.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to hapro
Regarding apache2, https://bz.apache.org/bugzilla/show_bug.cgi?id=57471
is still open, and I just tried a 2.4.38 build with pcre2, and it
doesn't work. Switching the task back to incomplete according to the bug
instructions.
** Changed in: apache2 (Ubuntu)
Status: Triaged => Incomplete
--
Seems a dupe to me.
For the bionic case, with keepalived < 2.0, is there some keepalived
script that can be run to restore the vip, after networkd removed it? We
could run it as a network-dispatcher hook then. Has this been
considered?
--
You received this bug notification because you are a memb
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:
Ins
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 a
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 a
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 subscr
** 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
** 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 Ca
** 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 Ca
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, wh
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
** C
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 cosmic
Do all of you have daily network restarts? What's the reason? Or was
this a one-off update that just by chance had a package upgrade that
required such a restart?
That being said, I of course agree that losing the virtual IP in such a
situation is bad.
--
You received this bug notification becau
MIR being prepared:
https://bugs.launchpad.net/ubuntu/+source/kronosnet/+bug/1811139
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1810844
Title:
libknet-dev universe d
Bug confirmed. It's an odd looking initscript, as it does not have the
usual actions in itself.
** Changed in: corosync (Ubuntu)
Status: New => Triaged
** Changed in: corosync (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ub
** Description changed:
corosync is a sync from debian, and in version 3.0.0-1 they added a
dependency on libknet-dev (kronos net). In Ubuntu, libknet-dev is in
universe.
https://salsa.debian.org/ha-team/corosync/commit/ca28efda4c8647ba262367c076e54d4787f529e0
https://salsa.debian.o
** Description changed:
corosync is a sync from debian, and in version 3.0.0-1 they added a
dependency on libknet-dev (kronos net). In Ubuntu, libknet-dev is in
universe.
https://salsa.debian.org/ha-team/corosync/commit/ca28efda4c8647ba262367c076e54d4787f529e0
https://salsa.debian.o
Public bug reported:
corosync is a sync from debian, and in version 3.0.0-1 they added a
dependency on libknet-dev (kronos net). In Ubuntu, libknet-dev is in
universe.
https://salsa.debian.org/ha-team/corosync/commit/ca28efda4c8647ba262367c076e54d4787f529e0
https://salsa.debian.org/ha-team/corosy
That patch is applied upstream in the package shipped in bionic and
later
** Also affects: keepalived (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: keepalived (Ubuntu)
Status: Triaged => Fix Released
** Changed in: keepalived (Ubuntu Xenial)
Status: New
Thanks for the patch and testing instructions
** Tags added: bitesize server-next
** Changed in: keepalived (Ubuntu)
Status: Incomplete => Triaged
** Changed in: keepalived (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubun
For strongswan, I found a reference in a 2018 workshop to work on
xt_cluster support:
https://wiki.strongswan.org/projects/strongswan/wiki/Linux_IPsec_Workshop_2018
No open bug reports about moving from ipt_CLUSTERIP to xt_cluster, just
references in old bugs about how that was wanted, but just no
Can you share your config /etc/keepalived/keepalived.conf ?
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1800159
Title:
keepalived ip_vs
Status in keepalived packag
Thanks for filing this bug in Ubuntu, and providing a link to a patch.
This will need some backporting, but it's an excellent start.
Looks like even cosmic is affected, at version 1.3.9.
** Changed in: keepalived (Ubuntu)
Status: New => Triaged
** Changed in: keepalived (Ubuntu)
Import
I've seen the wget debian change, but just switching builddeps from pcre3-dev
to pcre2-dev and rebuilding isn't enough. The package ends up not finding pcre
and doesn't enable it:
checking for PCRE... no
checking pcre.h usability... no
checking pcre.h presence... no
checking for pcre.h... no
...
Artful is EOL.
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/ocfs2-tools/+git/ocfs2-tools/+merge/351821
** Changed in: ocfs2-tools (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
High
Thanks for filing this bug in Ubuntu.
This is the error reported in the logs:
Setting up haproxy (1.8.8-1ubuntu0.1) ...
Job for haproxy.service failed because the control process exited with error
code.
See "systemctl status haproxy.service" and "journalctl -xe" for details.
invoke-rc.d: initscri
Thanks for filing this bug in Ubuntu.
This is the error log:
Setting up haproxy (1.8.8-1ubuntu0.1) ...
Job for haproxy.service failed because the control process exited with error
code.
See "systemctl status haproxy.service" and "journalctl -xe" for details.
invoke-rc.d: initscript haproxy, actio
** Changed in: heartbeat (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to heartbeat in Ubuntu.
https://bugs.launchpad.net/bugs/1735355
Title:
heartbeat: port to Python3
Status in hear
Thanks for filing this bug in Ubuntu.
I tried a simple case of bringing up two lxd containers, one with
haproxy as the frontend, another one with just apache as the backend,
and this config file on the frontend:
(defaults from the package go here)
frontend mycontainer
bind *:9090
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1747411
Title:
Change of default database file format to SQL
Status in certmonger package in U
Bionic was released with 1.8.8-1, sync from debian.
** Changed in: haproxy (Ubuntu)
Status: Fix Committed => Fix Released
--
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/b
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 Ubuntu
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 backen
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 the
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 r
** 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
High Availability Team, which is subscribed to hapr
Public bug reported:
o2image fails on s390x:
dd if=/dev/zero of=/tmp/disk bs=1M count=200
losetup --find --show /tmp/disk
mkfs.ocfs2 --cluster-stack=o2cb --cluster-name=ocfs2 /dev/loop0 # loop dev
found in prev step
Then this comand:
o2image /dev/loop0 /tmp/disk.image
Results in:
Segmentation
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to ocfs2-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1740927
Title:
FTBFS: unknown type name ‘errcode_t’
Status in ocfs2-tools package in Ubuntu:
In
PPA with test packages:
https://launchpad.net/~ahasenack/+archive/ubuntu/ocfs2-tools-
ftbfs-1740927/ (still building atm)
** Description changed:
gcc -g -O2 -fdebug-prefix-map=/home/ubuntu/x/ocfs2-tools-1.8.5=.
-fstack-protector-strong -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-
artful has the same bug, but it's not worth an SRU just because of this.
I nominated artful, however, so that if an SRU is ever done, this bug
will show up and the fix is here.
** Also affects: ocfs2-tools (Ubuntu Artful)
Importance: Undecided
Status: New
--
You received this bug noti
Affects: ocfs2-tools (Ubuntu)
Importance: Low
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Changed in: ocfs2-tools (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which
The development seems to be happening here:
https://github.com/markfasheh/ocfs2-tools
Might be worth filing a bug there:
https://github.com/markfasheh/ocfs2-tools/issues
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to ocfs2-
I'll set the bug status to "incomplete" pending further information, but
it looks like haproxy is behaving according to the documentation.
If you believe that's not the case, please attach a full haproxy.cfg
config file so we can inspect what is going on.
On the other hand, you think it's a behav
Sorry for taking to long to get back to this bug.
>From the haproxy documentation
>(http://cbonte.github.io/haproxy-dconv/1.6/configuration.html#4.2-email-alert%20level):
"""
Alerts are sent when :
* An un-paused server is marked as down and is alert or lower
* A paused server is marked as down
This worked for me in trusty with the proposed cloud-archive repository.
Before, when I restarted haproxy, I got an extra process:
root@juju-machine-2-lxc-0:~# service haproxy restart
* Restarting haproxy haproxy
...done.
root@juju-machine-2-lxc-0:~# ps fxaw|grep haproxy
32215 ?Ss
** Summary changed:
- Stop doesn't works on Trusty
+ Stop doesn't work on Trusty
--
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/1477198
Title:
Stop doesn't work on Trust
** Tags added: kanban-cross-team
--
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/1477198
Title:
Stop doesn't work on Trusty
Status in Ubuntu Cloud Archive:
Confirmed
St
** Changed in: landscape/release-29
Status: Fix Committed => Fix Released
** Changed in: landscape
Status: Fix Committed => Fix Released
** Changed in: landscape
Milestone: 15.08 => 15.07
--
You received this bug notification because you are a member of Ubuntu
High Availabilit
** Changed in: landscape/cisco-odl
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1490727
Title:
"Invalid IPC credentials" a
** Changed in: landscape
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1490727
Title:
"Invalid IPC credentials" after coros
** Changed in: landscape/release-29
Status: New => In Progress
** Changed in: landscape/release-29
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: landscape
Status: New => In Progress
** Changed in: landscape
Assignee: (unassigned) =
** Changed in: landscape/cisco-odl
Status: New => In Progress
** Changed in: landscape/cisco-odl
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: landscape/cisco-odl
Milestone: None => falkor-0.9
--
You received this bug notification because
84 matches
Mail list logo
