Server Bug triage Monday 7th feb 2022

Bryce Harrington bryce.harrington at
Mon Feb 7 17:40:01 UTC 2022

On Mon, Feb 07, 2022 at 11:05:46AM +0100, Christian Ehrhardt wrote:
> Hi,
> today's bug triage presented to me 18 bugs of which most looked under
> control and on a way to be resolved.
> Out of the recent cases here a few worth to mention
> Keepalived - Doesnt regain quorum when tracked process restarts Edit
> Bug with an upstream fix that we should backport, I've triaged and
> assigned Lucas to complete the triage in case there is any
> context-expert overruling of my assumptions.
> Rsync - rsync hangs on select(5, [], [4], [], {60, 0} Edit
> Miriam found the case and an upstream fix, she also grabbed this to
> prepare an SRU \o/
> Openssh - SSH 1.99 clients fail to connect to openssh-server
> SEG picked up a fix that I had prepared almost two years ago. Back
> then this died by a lack of community participation, but SEG brought
> the need to continue on this case.
> Exim4 - PROXY feature not compiled i
> This is a request for new features, Bryce correctly suggested to
> handle this together in Debian but it seems nothing happened. We might
> need to help to carry over the request.

In principle, I find it works a lot better for the original reporter to
champion the new feature in debian or upstream, unless the issue is
obvious, widespread, or easily reproduced.  But I've unexpired the bug
to give a 2nd chance since it does sound like a reasonable request, and
given some added directions on filing bugs with upstream:

I set to incomplete so it'll eventually re-expire, and we can
re-evaluate again.

> Long term bugs not touched for a while and worth to mention
> squid - squid does not accept WCCP of Cisco router since 3.5.27
> Sergio did the initial work and tracks upstream, but there seems to be
> no recent progress on
> anymore :-/
> mysql - Cannot connect anymore to Azure Database for MySQL with 8.0.27
> This is about a regression in release by a security update that breaks
> Focal<->Azure Database
> Unfortunately upstream/Microsoft seem to have settled on now being incompatible
> There is an Azure DB "Flexible Server" instead of "Single Server"
> which will work, but I'm unsure how to handle that from Ubuntu's POV.
> Lars/Robie/Lena (for mysql) and Marc (for security) do you have
> opinions/guidance on next steps for that?
> -----------
> General bug triage for mysql
> We have never really completed :-/
> Nowadays we still have a lot of common cases to duplicate and the old list being
> no more is helpful.
> I've used the heat ordered last cases on mysql-8.0 to look for
> duplicate candidates
> But I wonder if we should revamp or remove that wiki page and what
> else wed want to come up as the need to find mysql bugs to duplicate
> new cases to is a common one.

I'm always a +1 to documenting, whether for processes or knowledge
sharing.  However, I do note the general intention has been to deprecate  So maybe instead of a wiki page, the relevant
information could be moved to debian/<something>, or if it's more
strongly ubuntu packaging process related, to the Ubuntu Maintainers'
Handbook?  The first 4 sections on that wiki page sound like they'd fit
well to the former, while the last section sounds more like a subsection
for UMH's Bug Triage section (and one that could perhaps be expanded now
that we know more).


> -- 
> Christian Ehrhardt
> Staff Engineer, Ubuntu Server
> Canonical Ltd
> -- 
> ubuntu-server mailing list
> ubuntu-server at
> More info:

More information about the ubuntu-server mailing list