This looks good, thanks!
One minor note. The dep3 header says: Origin: upstream,
https://github.com/haproxy/haproxy/commit/d9a130e1962c2a5352f33088c563f4248a102c48;
however that link says "This commit does not belong to any branch on
this repository." so it isn't technically "upstream". However,
Hello Simon, or anyone else affected,
Accepted haproxy into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/haproxy/1.8.8-1ubuntu0.11 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Based on the upstream report this doesn't appear to be arm64 specific.
** Tags added: bitesize server-next
** Changed in: haproxy (Ubuntu)
Status: New => Triaged
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
** Summary changed:
- haproxy crashes on arm64 in
** Tags removed: server-triage-discuss
--
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/1437359
Title:
A PIDFILE is double-defined for the corosync-notifyd init script
> From my understanding this means that supporting an alternative init
system is optional ("Packages may include support for alternate init
systems besides systemd"). So basically this is up to the package
maintainer whether or not the package should support an alternative init
system.
I'm not
Hello David, or anyone else affected,
Accepted haproxy into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/haproxy/1.8.19-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello David, or anyone else affected,
Accepted haproxy into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/haproxy/1.8.8-1ubuntu0.6 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello David, or anyone else affected,
Accepted haproxy into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/haproxy/2.0.5-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: bionic-openssl-1.1
--
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/1841936
Title:
Rebuild haproxy with openssl 1.1.1 will change features (bionic)
Status
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:
The SRU team discussed this last week and we agreed that enabling TLS
1.3 is appropriate.
> [Test Case]
> * run "haproxy -vv" and check the reported TLS versions to include 1.3
I think we should additionally check during SRU verification that TLS
functionality is working correctly, both with an
Note that if this turns out to be challenging a "force-badtest" is
likely to be acceptable to get the package migrated for now.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
When you update with details, please make sure to provide full
reproduction steps and include details of the Ubuntu release and package
versions you used. When done, please change the bug status back to New,
and
Am I right in thinking that the limits being too low are causing false
positives in autopkgtests?
If so, we could check the limits in the test themselves and skip (exit
77 and declare "skippable") if on armhf and the limits aren't high
enough. That's a reasonable action for the packages, I think.
It looks like there is some clear and actionable work in keepalived here
(even if as a workaround and the real fix ends up being in systemd), so
I'm marking it as Triaged.
FTR, the Ubuntu Server Team is aware of this as a high level issue and
it is high up in our list of priorities to determine
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
In which Ubuntu release are you asking for the update? If a stable
release, please start by reading
https://wiki.ubuntu.com/StableReleaseUpdates - we certainly won't do it
without any justification, so please
** Tags removed: 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/1810583
Title:
Daily cron restarts network on unattended updates but keepalived
Great, thanks!
--
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 does not autoload the ip_vs kernel module when it is
required
Status in
Reproduced with your keepalived.conf, thanks - specifically that what
goes to syslog seems to be a problem on startup without ip_vs manually
loaded, and after a manual modprobe there is less of an error (I get
other errors presumably because I don't have your network set up).
I'm surprised to
** 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
** Bug watch added: Debian Bug tracker #888747
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888747
** Also affects: keepalived (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888747
Importance: Unknown
Status: Unknown
** Summary changed:
- keepalived ip_vs
+
** Tags added: regression-update
--
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/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
Status in
Marking Incomplete. See my comment 5. If this is still an issue, please
explain and set the bug status back to New. Thanks!
** Changed in: keepalived (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
High Availability Team,
Please do not change the bug status away from Incomplete until you have
responded to the questions Christian raised in comment 2.
** Changed in: haproxy (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
High Availability
** Changed in: keepalived (Ubuntu Xenial)
Status: Triaged => Incomplete
** Changed in: keepalived (Ubuntu Trusty)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in
** Changed in: keepalived (Ubuntu Xenial)
Assignee: (unassigned) => Joshua Powers (powersj)
--
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/1583503
Title:
** Changed in: pacemaker (Ubuntu)
Importance: Undecided => High
** Tags added: bitesize server-next
--
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/1595901
Title:
Uploaded, thanks.
** Changed in: cluster-glue (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to cluster-glue in Ubuntu.
https://bugs.launchpad.net/bugs/1590208
Title:
needs a
** Also affects: haproxy (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: haproxy (Ubuntu Trusty)
Status: New => Triaged
** Changed in: haproxy (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: haproxy (Ubuntu Trusty)
Assignee: (unassigned)
** Changed in: haproxy (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
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/1524635
Title:
haproxy syslog
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Yakkety has 1.2.20, so this is Fix Released. You asked for a backport
but you haven't said what package version you're using, what release you
want the fix backported to or in which releases you have confirmed the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It looks like you're using a version of haproxy from a PPA, rather than
the package shipped with Ubuntu? In this case we can't treat this as a
bug in Ubuntu, so I'm marking this bug filed against haproxy in Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It looks like keepalived has a systemd service definition file now, and
Xenial uses systemd. So presumably this is moot now, as on Ubuntu salt
(I presume) will be able to use systemd's service status?
--
You
Thanks. Since this is then presumed fixed in Xenial which is at
1.1.12-0ubuntu3, I'm marking this bug as Fix Released. If you would like
this fix backported to 14.04 then someone needs to prepare a backport as
described in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.
I'll leave a task
** Changed in: haproxy (Ubuntu)
Importance: Undecided => Medium
** Tags added: bitesize
--
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/1524635
Title:
haproxy syslog
Thanks, marking this as Invalid based on Mark's reply.
** Changed in: haproxy (Ubuntu)
Status: New => Invalid
--
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/1334958
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
By "make sure that below patch has been used on above environment" do
you mean that you are running a patched version of haproxy, or are you
proposing that this patch fixes the bug that you are reporting?
Is
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This seems like to be an upstream bug and if it can be confirmed to be
then should be reported there, and we can backport any fix to Ubuntu as
required.
However Lucid is EOL now. If this bug still affects a
Louis,
I can't sponsor your debdiff into backports, but be careful of ordering
issues in your patch. clean() should be defined before the trap is set,
and tmp should be defined before any point that clean() could be called.
In general you should quote "$tmp" as well in case it ends up with
spaces
Please could you complete the bug report from the perspective of the
pacemaker task? I don't think there's enough here to go on for example
in a way that upstream or the Debian maintainer would understand.
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Incomplete
--
You received
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
We're in sync with Debian on the haproxy package so this bug should be
reported there. For Ubuntu, managing haproxy with systemd units would
presumably be easiest; this could also be contributed to Debian.
*** This bug is a duplicate of bug 1488453 ***
https://bugs.launchpad.net/bugs/1488453
** This bug has been marked a duplicate of bug 1488453
Package postinst always fail on first install when using systemd
--
You received this bug notification because you are a member of Ubuntu
High
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
In Ubuntu we do not update stable releases with new upstream versions in
order to keep stable releases stable, and keepalived in Ubuntu does not
currently have an exception on this. See
** Tags removed: server-next
--
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/1481337
Title:
keepalived makes a floating IP available on more than one host after
** Package changed: haproxy (Ubuntu) = trusty-backports
--
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/1472713
Title:
HAProxy 1.5.3 requires security updates
Status in
Following Debian as I don't think it's appropriate for Ubuntu to diverge
from Debian on this point. We'll follow whatever Debian does.
** Changed in: haproxy (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
High Availability Team,
Thanks Ante. Though this is a regular update, not a security one.
** Summary changed:
- Security update breaks pacemaker in 14.04
+ SRU breaks pacemaker in 14.04
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
High Availability Team,
I posted https://lists.ubuntu.com/archives/ubuntu-
release/2014-July/002967.html
12:37 rbasak doko: while you're looking, there was also
https://lists.ubuntu.com/archives/ubuntu-release/2014-July/002967.html
12:37 rbasak New dependencies on haproxy-doc, pulling in nodejs of all
Also, I didn't check if the init.d script is provided by packaging or
comes directly from upstream. If it comes directly from upstream, then
sending the patch upstream directly would be best.
** Changed in: haproxy (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
haproxy in Ubuntu is currently identical to the Debian haproxy package
from which it is derived, so it seems likely to me that Debian will
benefit from this patch, too. I would also like to avoid the additional
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please see the stable release update policy, rationale and procedure
documented at: https://wiki.ubuntu.com/StableReleaseUpdates
In particular, I see changelog entries such as some cosmetics., which
do not appear
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I guess that update-rc.d can be run by hand as a workaround? In this
case, setting Importance: Medium as a workaround is available.
** Changed in: pacemaker (Ubuntu)
Importance: Undecided = Medium
--
You
** Tags added: hwe-dkms
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1204459
Title:
Please package drbd tools v8.4 for use with Raring LTS Enablement
Stacks
Status in
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
keepalived is already packaged, but I can see that upstream version
1.2.7 is available. Ubuntu and Debian have 1.2.2; 1.2.6 is available in
experimental.
Please specify which upstream release you are requesting,
Lionel,
I've uploaded 2:8.4.3-0ubuntu1~ppa2 to my PPA
(https://launchpad.net/~racb/+archive/experimental). This merges changes
in Debian's 8.3.13-2, which includes turning off the kernel version
check. Please could you check that this works as you expect; then we can
get it uploaded? Thanks!
--
PS. the package is still in the build queue; it should be done in about
an hour.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1132302
Title:
drbd8-utils are not
(Ubuntu Raring)
Assignee: Robie Basak (racb) = (unassigned)
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1132302
Title
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I think this needs attention, so setting Importance to High. Usually SRU
policy generally frowns on this kind of update, but it may make sense
given that the kernel is being bumped. I appreciate you bringing it
** Changed in: keepalived (Ubuntu)
Status: Incomplete = New
** Changed in: keepalived (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to keepalived in Ubuntu.
60 matches
Mail list logo
