Re: Monday triage 2024-03-18

[Lucas Kanashiro]

Hi,

On Tue, Mar 19, 2024 at 3:35 PM Lena Voytek 
wrote:

> LP: #2049197  - ruby3.0 -
> ruby_xfree segmentation fault
> This one could also use an update on our end
>

I re-triagged this bug, assigned it to myself and tagged it as server-todo.

Thanks for the heads up.

Lucas Kanashiro.
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Sergio Durigan Junior]

On Monday, February 26 2024, Athos Ribeiro wrote:

> https://pad.lv/2054632 | libvirt |   ninja command failing 
> for upstream libvirt compilation |
>   There is a fix submitted by Frank Heimes for this one. I added this to our
>   backlog.

This is on my radar.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report (2023-09-05)

[Sergio Durigan Junior]

On Wednesday, September 06 2023, Bryce Harrington wrote:

> Discourse Comment Triage Helper
> Showing comments belonging to the Server category on 
> https://discourse.ubuntu.com, updated between 2023-09-01 (Friday) and 
> 2023-09-04 (Monday) inclusive
> Third party repository us… [Sergio Durigan Junior] 
> └─ +95926 [David Mohammed, 2023-09-02] 
>   - Already answered by sergio
>   - If add-apt-repository is indeed deprecated as suggested, that might
> be impactful to us.  This might be worth further investigation.

I already replied on ~server-vip, but just to make it more visible: I
raised this question yesterday on #ubuntu-devel, and the official answer
(from Julian) is that add-apt-repository will *not* be deprecated and is
still the recommended way to add PPAs to one's system.  Having said
that, there are certain functionalities of add-apt-repository (not
related to PPA support) that can be considered as deprecated.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage

[Sergio Durigan Junior]

On Monday, August 28 2023, Mitchell Dzurick wrote:

> LP: #2028124 
> | apt dist-upgrade does not restart package qemu-guest-agent
> Needs work. This issue is fixed in Mantic now. Need to determine if an SRU
> is worth it. A user recently mentioned a non-trivial issue due to this bug
> when interacting with terraform that could justify an SRU.

Agreed.  I will work on SRUing the bug this week/the next as time
permits.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2023-08-14)

[Bryce Harrington]

On Mon, Aug 14, 2023 at 02:59:26PM -0400, Sergio Durigan Junior wrote:
> ### https://pad.lv/2031094 | New | mysql-8.0 | package mysql-server-8.0
> 8.0.33-0ubuntu0.22.04.4 failed to … |
> 
> Incomplete.  These mysql timeout bugs are annoying because there's not
> much I can do to investigate them.

Yeah you're right, and I concur with your investigation.  Unfortunately
we'll almost certainly not get anything further from the reporter, as is
usually the case...

Looking at the dpkg history log here, it looks like the user was setting
up a laptop(?), possibly had trouble with their hardware (evidenced by
repeated reinstalls of fwupd), then the next day they installed mysql,
purged it, reinstalled, then hit the issue.  Could the "File exists"
error be due to something leftover from the attempted purge?

Didn't we have a bug about install->purge->reinstall->crash?  I'm not
spotting an obvious one open against mysql-8.0 but we've certainly seen
variations of this pattern.

Bryce

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2023-08-14)

[Lucas Kanashiro]

Hi,

On Mon, Aug 14, 2023 at 3:59 PM Sergio Durigan Junior <
sergio.duri...@canonical.com> wrote:

>
> ### https://pad.lv/1946376 | New | golang-github-cont… | FTBFS due to
> conflict with vendored source in docker.io |
>
> With the advent of docker.io-app, I'm wondering if this one could be
> marked as Fix Released for everything.  Cc'ing Lucas who might know
> more.
>

You are right. I updated the bug and marked it as Fix Released.

Thanks for the heads-up :)
Lucas Kanashiro.
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Athos Ribeiro]

On Mon, Aug 07, 2023 at 03:40:50PM +0100, Robie Basak wrote:

On Mon, Aug 07, 2023 at 10:57:04AM -0300, Athos Ribeiro wrote:

Bugs last updated between 2023-08-04 (Friday) and 2023-08-06 (Sunday) inclusive
Date range identified as: "Monday triage"

https://pad.lv/2029431 | libslirp | Provide static library in libslirp-dev
  This is a request to ship a static library in the -dev binary package.
  AFAICT, the request makes sense. However, I did not move this one to triaged
  and added to the backlog because it would be nice to get someone with more
  context here (qemu) before we commit to changing the package.


OK, but this question will get lost unless we track it in some list or
other. Would you like to add it to server-triage-discuss, or something
else?


I was expecting that discussing it in this thread would  be enough to
generate answers. But then, indeed, there's always the risk it gets lost
if we get no replies. Added the triage discuss tag.

--
Athos Ribeiro

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Robie Basak]

On Mon, Aug 07, 2023 at 10:57:04AM -0300, Athos Ribeiro wrote:
> Bugs last updated between 2023-08-04 (Friday) and 2023-08-06 (Sunday) 
> inclusive
> Date range identified as: "Monday triage"
> 
> https://pad.lv/2029431 | libslirp | Provide static library in libslirp-dev
>   This is a request to ship a static library in the -dev binary package.
>   AFAICT, the request makes sense. However, I did not move this one to triaged
>   and added to the backlog because it would be nice to get someone with more
>   context here (qemu) before we commit to changing the package.

OK, but this question will get lost unless we track it in some list or
other. Would you like to add it to server-triage-discuss, or something
else?

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage

[Lena Voytek]

On Mon, 2023-07-17 at 15:44 -0700, Bryce Harrington wrote:
> Bugs last updated between 2023-07-14 (Friday) and 2023-07-16 (Sunday)
> inclusive
> Found 24 bugs
> 
> Only 3 of the 24 required triage attention, rest are already
> processing:
> 
> LP: #2027838  libvirt-uri-sh overrides configured default
>   --> Tagged server-triage-discuss for Wednesday's meeting.
>   - This script is an adaptor for xen, which I wonder if is an
> obsolete
>     use case?  If so, reporter's suggestion to drop it might be
> valid.
> 
> LP: #2027921  chrony failed to install due to conflict with systemd
>   --> Incomplete
>   - Asked reporter for some further clarifications.
>   - I am not seeing other reports of this problem, so suspect it may
> be
>     something unique to the reporter.  Neither logs nor report are
>     detailed enough to make educated guesses yet.
> 
> LP: #2027913  mysql-8.0  Failed to install
>   --> Duped to LP: #1914636.  Most likely just a dupe of that.
>   - I noticed LP: #2002828 also probably another dupe and duped it
>   - source_mysql-8.0.py already has a check + prompt for missing
>     /etc/mysql, perhaps that could be broadened to look for
>     /etc/mysql/conf.d/ as well?  I.e. something like:
> 
>     if not os.path.isdir('/etc/mysql'):
>     ## ...
>     else if not os.path.isdir('/etc/mysql/conf.d'):
>     report['EtcMysqlConfdDirListing'] = str(False)
>     response = ui.yesno("The /etc/mysql/conf.d directory is
> missing, which "
>     "suggests a local configuration problem
> rather "
>     "than a bug in Ubuntu (see LP: #1914636).
> "
>     "Do you still wish to "report this bug?")
>     if not response: # user cancelled or answered
> No 
>     report['UnreportableReason'] = "Missing /etc/mysql/conf.d
> directory"
>     return False
>     else:
>     ## ...
> 
>     Lena, what do you think?

That sounds like a good idea to me. It should help mitigate bad reports
in the future. I'll add it in once the dust is settled from the
upcoming 8.0.34 security release.
 
> 
> 
> Discourse Comment Triage Helper
> Showing comments belonging to the Server category on
> https://discourse.ubuntu.com, updated between 2023-07-14 (Friday) and
> 2023-07-16 (Sunday) inclusive
> Get started with LAMP app… [Joshua Powers] 
> └─ 86256 [Allynna McCleod] 
>    └─ 91509 [Sally Makin] 
>   └─ +92415 [Volvodemort, 2023-07-16] 
> ROCK Images - Introduction [Bryce Harrington] 
> └─ 92100 [Seth Arnold] 
>    └─ 92292 [Samirakarioh] 
>   └─ 92293 [Seth Arnold] 
>  └─ +92299 [Cristovao Cordeiro, 2023-07-14] 
> 
> The first item relates to use of tasksel, which I am not accustomed
> to
> so am unclear on how it should be used on modern systems.  I've
> updated
> the docs to address the mentioned error, however I'm unclear if
> tasksel
> is actually doing anything or if it is broken... or unnecessary.
> 
> Is tasksel only included for legacy purposes at this point, or is it
> a
> workflow we actively support?  If the former, maybe it should be
> dropped
> from the docs; if the latter than perhaps the tasksel workflow needs
> some further attention?
> 
> Bryce
> 


-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2023-06-26)

[Andreas Hasenack]

Hi

On Tue, Jun 27, 2023 at 3:24 AM Christian Ehrhardt
 wrote:
>
> On Mon, Jun 26, 2023 at 10:20 PM Sergio Durigan Junior
>  wrote:
> >
> > On Monday, June 26 2023, I wrote:
> >
> > > Bug Triage
> > > ==
> > >
> > > ### https://pad.lv/1991441 | Confirmed | glusterfs | glusterd and
> > > glusterfs crashes after dist-upgrade from foca… |
> > >
> > > armhf + illegal instruction = fun.  I subscribed ubuntu-server, but I
> > > don't have an armhf system available to test the problem.  I'll see if I
> > > can reserve one.
> >
> > I looked into this one and posted my findings there.
>
> Interesting Sergio,
> I wonder if
> https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1991441/comments/5
> into
> https://github.com/gluster/glusterfs/issues/3911
> into
> https://github.com/gluster/glusterfs/issues/702
>
> Doesn't this sort of imply we should remove armhf binaries from
> glusterfs going forward.
> If there can be a fix for the problem that is there in the existing
> versions affected (jammy AFAICS) great, we'll serve it.
> But going forward more of that is gonna happen.
>
> WDY(all)T of removing armhf in glusterfs in >Mantic and asking Debian
> if they want to do the same?

+1, I had an encounter with armhf incompatibility before[1] in
glusterfs, which was fixed, but at that time upstream already said
that it was pure luck it was fixed, because they don't care about
32bits.


1. https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1951408

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2023-06-26)

[Christian Ehrhardt]

On Mon, Jun 26, 2023 at 10:20 PM Sergio Durigan Junior
 wrote:
>
> On Monday, June 26 2023, I wrote:
>
> > Bug Triage
> > ==
> >
> > ### https://pad.lv/1991441 | Confirmed | glusterfs | glusterd and
> > glusterfs crashes after dist-upgrade from foca… |
> >
> > armhf + illegal instruction = fun.  I subscribed ubuntu-server, but I
> > don't have an armhf system available to test the problem.  I'll see if I
> > can reserve one.
>
> I looked into this one and posted my findings there.

Interesting Sergio,
I wonder if
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1991441/comments/5
into
https://github.com/gluster/glusterfs/issues/3911
into
https://github.com/gluster/glusterfs/issues/702

Doesn't this sort of imply we should remove armhf binaries from
glusterfs going forward.
If there can be a fix for the problem that is there in the existing
versions affected (jammy AFAICS) great, we'll serve it.
But going forward more of that is gonna happen.

WDY(all)T of removing armhf in glusterfs in >Mantic and asking Debian
if they want to do the same?

> --
> Sergio
> GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam



-- 
Christian Ehrhardt
Senior Staff Engineer and acting Director, Ubuntu Server
Canonical Ltd

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2023-06-26)

[Sergio Durigan Junior]

On Monday, June 26 2023, I wrote:

> Bug Triage
> ==
>
> ### https://pad.lv/1991441 | Confirmed | glusterfs | glusterd and
> glusterfs crashes after dist-upgrade from foca… |
>
> armhf + illegal instruction = fun.  I subscribed ubuntu-server, but I
> don't have an armhf system available to test the problem.  I'll see if I
> can reserve one.

I looked into this one and posted my findings there.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Mauricio Oliveira]

On Tue, May 16, 2023 at 6:01 PM Bryce Harrington
 wrote:
>
> On Tue, May 16, 2023 at 01:41:52PM -0300, Athos Ribeiro wrote:
> > On Tue, May 16, 2023 at 12:24:21PM -0300, Mauricio Oliveira wrote:
> > > On Mon, May 15, 2023 at 12:29 PM Athos Ribeiro
> > >  wrote:
> > > > https://pad.lv/2017701 | ipmitool | Multiple options= are parsed 
> > > > incorrectly making setting per…
> > > >Matthew Ruffell attached a few debdiffs and filled in the paperwork 
> > > > for
> > > >SRUing a fix here. He may bee needing a sponsor.
> > >
> > > Thanks for checking this!  Sorry, I think the SRU is waiting on test 
> > > results,
> > > according to an internal tracker, but that information isn't available
> > > in the bug.
> > > Matthew is from SEG, so our sponsors can review/upload to stable releases.
> >
> > OK
> >
> > > If there's anything we can do in the future to help save server triage 
> > > time,
> > > please just let me know. It may be as simple as just adding a comment or
> > > something in the description, or unsubscribing ~ubuntu-server, if you 
> > > want.
> >
> > Maybe someone else from server want to chime in on this one, but just
> > stating that  the attached patches should be reviewed/uploaded by a
> > specific team should do it. Since they were just attached there, I was
> > wondering if that also implied a request for sponsorship.
>
> Yep, agreed with Athos, just leave a note.  Purpose of triage is to do a
> quick check that things are being covered so having this pop up is
> entirely within scope, even when there's no action needed by us.
> But I think it's also ok to ubsubscribe ~ubuntu-server for things that
> you know definitely don't need to be on the server team's radar.

Ack; thanks, Bryce!

>
> Bryce
>
> > > Thanks!
> > > Mauricio
> >
> > Thanks for taking the time to clear this one out :)
> >
> > [snip]
> >
> > --
> > Athos Ribeiro
> >
> > --
> > ubuntu-server mailing list
> > ubuntu-server@lists.ubuntu.com
> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> > More info: https://wiki.ubuntu.com/ServerTeam



-- 
Mauricio Faria de Oliveira

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Bryce Harrington]

On Tue, May 16, 2023 at 01:41:52PM -0300, Athos Ribeiro wrote:
> On Tue, May 16, 2023 at 12:24:21PM -0300, Mauricio Oliveira wrote:
> > On Mon, May 15, 2023 at 12:29 PM Athos Ribeiro
> >  wrote:
> > > https://pad.lv/2017701 | ipmitool | Multiple options= are parsed 
> > > incorrectly making setting per…
> > >Matthew Ruffell attached a few debdiffs and filled in the paperwork for
> > >SRUing a fix here. He may bee needing a sponsor.
> > 
> > Thanks for checking this!  Sorry, I think the SRU is waiting on test 
> > results,
> > according to an internal tracker, but that information isn't available
> > in the bug.
> > Matthew is from SEG, so our sponsors can review/upload to stable releases.
> 
> OK
> 
> > If there's anything we can do in the future to help save server triage time,
> > please just let me know. It may be as simple as just adding a comment or
> > something in the description, or unsubscribing ~ubuntu-server, if you want.
> 
> Maybe someone else from server want to chime in on this one, but just
> stating that  the attached patches should be reviewed/uploaded by a
> specific team should do it. Since they were just attached there, I was
> wondering if that also implied a request for sponsorship.

Yep, agreed with Athos, just leave a note.  Purpose of triage is to do a
quick check that things are being covered so having this pop up is
entirely within scope, even when there's no action needed by us.
But I think it's also ok to ubsubscribe ~ubuntu-server for things that
you know definitely don't need to be on the server team's radar.

Bryce

> > Thanks!
> > Mauricio
> 
> Thanks for taking the time to clear this one out :)
> 
> [snip]
> 
> -- 
> Athos Ribeiro
> 
> -- 
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Mauricio Oliveira]

On Tue, May 16, 2023 at 1:41 PM Athos Ribeiro
 wrote:
>
> On Tue, May 16, 2023 at 12:24:21PM -0300, Mauricio Oliveira wrote:
> >Hi Athos,
>
> Hi!
>
> >On Mon, May 15, 2023 at 12:29 PM Athos Ribeiro
> > wrote:
> >>
> >> Bugs last updated between 2023-05-12 (Friday) and 2023-05-14 (Sunday) 
> >> inclusive
> >> Date range identified as: "Monday triage"
> >>
> >> https://pad.lv/2017701 | ipmitool | Multiple options= are parsed 
> >> incorrectly making setting per…
> >>Matthew Ruffell attached a few debdiffs and filled in the paperwork for
> >>SRUing a fix here. He may bee needing a sponsor.
> >>
> >
> >Thanks for checking this!  Sorry, I think the SRU is waiting on test results,
> >according to an internal tracker, but that information isn't available
> >in the bug.
> >Matthew is from SEG, so our sponsors can review/upload to stable releases.
>
> OK
>
> >If there's anything we can do in the future to help save server triage time,
> >please just let me know. It may be as simple as just adding a comment or
> >something in the description, or unsubscribing ~ubuntu-server, if you want.
>
> Maybe someone else from server want to chime in on this one, but just
> stating that  the attached patches should be reviewed/uploaded by a
> specific team should do it. Since they were just attached there, I was
> wondering if that also implied a request for sponsorship.
>

Ack; thanks. Indeed, I'd think the same, myself.

> >Thanks!
> >Mauricio
>
> Thanks for taking the time to clear this one out :)

Happy to help, and sorry for the hiccup on our side.

>
> [snip]
>
> --
> Athos Ribeiro



-- 
Mauricio Faria de Oliveira

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Athos Ribeiro]

On Tue, May 16, 2023 at 12:24:21PM -0300, Mauricio Oliveira wrote:

Hi Athos,


Hi!


On Mon, May 15, 2023 at 12:29 PM Athos Ribeiro
 wrote:


Bugs last updated between 2023-05-12 (Friday) and 2023-05-14 (Sunday) inclusive
Date range identified as: "Monday triage"

https://pad.lv/2017701 | ipmitool | Multiple options= are parsed incorrectly 
making setting per…
   Matthew Ruffell attached a few debdiffs and filled in the paperwork for
   SRUing a fix here. He may bee needing a sponsor.



Thanks for checking this!  Sorry, I think the SRU is waiting on test results,
according to an internal tracker, but that information isn't available
in the bug.
Matthew is from SEG, so our sponsors can review/upload to stable releases.


OK


If there's anything we can do in the future to help save server triage time,
please just let me know. It may be as simple as just adding a comment or
something in the description, or unsubscribing ~ubuntu-server, if you want.


Maybe someone else from server want to chime in on this one, but just
stating that  the attached patches should be reviewed/uploaded by a
specific team should do it. Since they were just attached there, I was
wondering if that also implied a request for sponsorship.


Thanks!
Mauricio


Thanks for taking the time to clear this one out :)

[snip]

--
Athos Ribeiro

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Mauricio Oliveira]

Hi Athos,

On Mon, May 15, 2023 at 12:29 PM Athos Ribeiro
 wrote:
>
> Bugs last updated between 2023-05-12 (Friday) and 2023-05-14 (Sunday) 
> inclusive
> Date range identified as: "Monday triage"
>
> https://pad.lv/2017701 | ipmitool | Multiple options= are parsed incorrectly 
> making setting per…
>Matthew Ruffell attached a few debdiffs and filled in the paperwork for
>SRUing a fix here. He may bee needing a sponsor.
>

Thanks for checking this!  Sorry, I think the SRU is waiting on test results,
according to an internal tracker, but that information isn't available
in the bug.
Matthew is from SEG, so our sponsors can review/upload to stable releases.

If there's anything we can do in the future to help save server triage time,
please just let me know. It may be as simple as just adding a comment or
something in the description, or unsubscribing ~ubuntu-server, if you want.

Thanks!
Mauricio




> ==
>
> Discourse Comment Triage Helper
> Showing comments belonging to the Server category, updated between 2023-05-12 
> (Friday) and 2023-05-14 (Sunday) inclusive
> [snip...]
>   └─ +89672 [Djbushby, 2023-05-13] 
> (https://discourse.ubuntu.com/t/11322/27)
>
> This is the comment added by the user:
>
> > “Below are links to the previous Ubuntu Server release server guides” 
> > missing for 20.04
>
> However, the guide makes no difference for 20.04 and later. I am unsure 
> whether
> we should just reply with this information or add a note to the page stating
> the fact.
>
>
> --
> Athos Ribeiro
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam



-- 
Mauricio Faria de Oliveira

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage

[Sergio Durigan Junior]

On Wednesday, January 04 2023, Bryce Harrington wrote:

> ### LP: #1908223 | Incomplete | nmap | 7.80 crashes with Assertion 
> `htn.toclock_running == true' 
>
> Already triaged by Paride, but commenter just repeated request for a
> fix.  Paride identified a possible commit.  I reiterated Paride's
> request and asked if a PPA with the patch would be good enough for their
> needs.

As a heads-up, I would like to ask the team to refrain from backporting
upstream patches for nmap until we can sort out the licensing situation.

Thanks,

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage

[Sergio Durigan Junior]

On Monday, December 12 2022, Lena Voytek wrote:

> LP: #1953128 
> - gcc-11 - GCC ICE: in create_fix_barrier, at config/arm/arm.c:17891
> Still seems to be a valid bug, may be worth looking into. @Sergio Durigan
> Junior  you may know more about this one.

Thanks, I'll have a look later.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Andreas Hasenack]

Hi,

On Mon, Nov 21, 2022 at 2:52 PM Athos Ribeiro 
wrote:

> Discourse Comment Triage Helper
> Showing comments belonging to the Server category, updated between
> 2022-11-18 (Friday) and 2022-11-20 (Sunday) inclusive
> Service - Kerberos with O… [Andreas Hasenack] (
> https://discourse.ubuntu.com/t/15356)
> └─ +82056 [Surfrock66, 2022-11-20] (
> https://discourse.ubuntu.com/t/15356/15)
>
>This is possibly a user with a configuration issue. I am unsure on how
> to
>proceed on this one. Should we ask them for more information in the
> discourse
>thread itself, ask them to file a bug or point the user to some user
> support
>channel?
>
>
I saw this one in my inbox, and didn't tend to it because a) it's the most
complicated setup we have in the guide; b) I would probably have to
redeploy that thing to understand the details of what he is asking.
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday triage report

[Robie Basak]

On Mon, Nov 21, 2022 at 02:51:03PM -0300, Athos Ribeiro wrote:
> Showing comments belonging to the Server category, updated between 2022-11-18 
> (Friday) and 2022-11-20 (Sunday) inclusive
> Service - Kerberos with O… [Andreas Hasenack] 
> (https://discourse.ubuntu.com/t/15356)
> └─ +82056 [Surfrock66, 2022-11-20] (https://discourse.ubuntu.com/t/15356/15)
> 
>   This is possibly a user with a configuration issue. I am unsure on how to
>   proceed on this one. Should we ask them for more information in the 
> discourse
>   thread itself, ask them to file a bug or point the user to some user support
>   channel?

IMHO, we should point them to community support resources like we do for
bugs. Otherwise they expect to get help in a place where there isn't
really any community hanging out, unlike the other places where the
community are active and help out. So it's beneficial to users to do
this, too.

Unless it's specifically an issue with the documentation, which some
proportion of things that initially look like support requests might
turn out to be.

Maybe we need to put together a template response for this kind of
thing.

Separately, Discourse has various moderation options. It might be
appropriate to split the comment out of the thread, maybe move it into
"Support Requests", and answer with a template there.


signature.asc
Description: PGP signature
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2022-11-14)

[Bryce Harrington]

On Wed, Nov 16, 2022 at 02:42:43PM -0500, Sergio Durigan Junior wrote:
> Bugs subscribed to ubuntu-server and not touched in 180 days
> 
> Found 2 bugs
> 
> ### https://pad.lv/1641238 | Triaged | apache2 | as a reverse proxy, a
> 100 continue response is sent prematu… |
> 
> Apparently there's an upstream fix for this one, but it seems that it's
> non-trivial to backport.  The only remaining task we have is for Bionic.
> I don't have the time to dive deeper here, unfortunately.

The last comment from a non-server team member was 2016, and the bug has
just one affected user.  This doesn't feel like it would be a good SRU
candidate.  I think it is not worth acting on until an affected user
reports in.

Bryce

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2022-11-14)

[Sergio Durigan Junior]

On Wednesday, November 16 2022, I wrote:

> ustriage found 9 bugs.  These are the noteworthy ones:
[...]

Lucas reminded me that I didn't include the dsctriage output in the
email.  Here it is:

Discourse Comment Triage Helper
Showing comments belonging to the Server category, updated between 2022-11-11 
(Friday) and 2022-11-13 (Sunday) inclusive
*Feedback: Subiquity part… [Znuff, 2022-11-11] 
(https://discourse.ubuntu.com/t/32167)

Therefore, nothing to do re. the discourse triage.

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14


signature.asc
Description: PGP signature
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2022-09-26)

[Robie Basak]

On Mon, Sep 26, 2022 at 02:34:43PM -0400, Sergio Durigan Junior wrote:
> ### https://pad.lv/1890263 - +(In Progress) [php-defaults] - release
> upgrade does not move to the new php apache mod
> 
> Last comment was from Christian, who said that they're waiting for Robie
> to sync with Steve on a final decision.  Maybe it's worth a followup
> from Robie?

I'm just in the middle here. I suggest Christian speaks to Steve
directly.


signature.asc
Description: PGP signature
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2022-03-14)

[Athos Ribeiro]

On Mon, Mar 14, 2022 at 05:41:21PM -0400, Sergio Durigan Junior wrote:

[snip...]



### https://pad.lv/1919965 - +(Triaged) [nginx] - nginx-common
   nginx.service comments use wrong signal

Another heads-up.  @Athos, you might want to ping the Salsa MR or submit
the patch via a Debian bug.


Thanks, Sergio. The salsa MR was merged and I added another comment
there so we can close this bug once 1.18.0-7 is sync'd or merged.


--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14




--
Athos Ribeiro

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage report (for: 2022-02-14)

[Lena Voytek]

On Mon, Feb 14, 2022 at 3:32 PM Bryce Harrington <
bryce.harring...@canonical.com> wrote:

> Found 17 bugs.  Ones of note:
>
> LP: #1831441 - *(Triaged)   [samba] - Please add
> WS-Discovery ( WSD ) support for Windows Samba s…
>   - A possible fix via addition of new package 'wsdd' has been packaged
> and submitted to Debian New.  It's awaiting processing.
>   - I've uploaded it to a PPA to check it'll build on LP.
>   - Reporter wishes for it to be in main for 22.04, but getting a MIR
> through in time seems ambitious.
>
> LP: #1946841 - (Incomplete) [amavisd-new]   - Merge amavisd-new
> from Debian unstable for 22.04
>   - There's a version in Debian now.
>   - Changed status to 'New'
>
> LP: #1958720 - (Confirmed)  [six]   - python3-yaml and
> python3-six are not co-installable with py…
>   - Patch on a plate (x2), however the fix is to remove Breaks to permit
> an obsolete package to remain present on an upgraded system.  I
> think this warrants a bit more discussion, so tagged
> 'server-triage-discuss'
>
> LP: #1960754 - (New)[samba] - gencache_init:
> Failed to create directory: /var/www/.cache/…
>   - Should have already been fixed in a security update from last
> November.  Asked user to verify what version they saw the issue, and
> if they've updated to current if the issue is resolved.
>
> LP: #1960088 - (New)[libapache2-mod-…]  - a) collections has
> no attribute callable; b) PY_SSIZE_T_CLE…
>
>
> #
> ### MySql Apport Bugs ###
> #
>
> LP: #1960739 - (New)[mysql-8.0] - package
> mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to …
>   - Looks like the user has upgraded since 13.10 and has a config
> setting that has become obsolete.  Lena, do you already have a bug
> report for collecting obsolete config values that need to be better
> filtered out or converted?  Sounds like query_cache_limit and
> expire-logs-days should be added to that list maybe?
>

The triage for this bug looks good to me. Looking into query_cache_limit
shows that it was deprecated as of MySQL 5.7.20, and removed altogether in
MySQL 8.0. So it seems like this is just a case of the configuration
breaking with an upgrade to focal and mysql 8.0. I don't have any other
bugs like it yet, but I'll keep it noted down in case similar ones pop up.

>
> ---
> Bugs tagged "-needs-merge -needs-sync -needs-oci-update -needs-snap-update
> -needs-mre-backport -needs-ppa-backport" and subscribed "ubuntu-server" and
> not touched in 60 days
> Found 2 bugs
> LP: #1320709 - (Triaged)[awstats]   - incorrect info in
> /usr/share/doc/awstats/README.Debian.gz a…
>   - This one looks resolved in newer releases.  Closed as fix released
>
> LP: #1953128 - (New)[gcc-11]- GCC ICE: in
> create_fix_barrier, at config/arm/arm.c:17891
>   - The gcc bug task remains open, but it's worked around for
> postgresql-14, so nothing left for us to do.
>
> ---
> Bugs subscribed to ubuntu-server and not touched in 180 days
> Found 0 bugs
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2021-09-27)

[Christian Ehrhardt]

On Mon, Sep 27, 2021 at 9:12 PM Sergio Durigan Junior
 wrote:
>
> ustriage found 21 bugs.  These are the noteworthy ones:
>
> ### https://pad.lv/1942195 - *+(Confirmed) [samba] - Installing Samba
> unexpectedly adds many unknown local users to sambashare group
>
> Paride submitted a proposal to the Debian samba package.  I will take a
> look later today.
>
>
> ### https://pad.lv/1944621 - (Confirmed) [openssh] - sshd in chroot has
> regression with glibc 2.34
>
> Pinged jawn-smith on #ubuntu-devel; he's on top of this one.
>
>
> ### https://pad.lv/1945013 - (New) [mysql-8.0] - mysql imposes a silent
> limit on passwords
>
> Wishlist IMO.
>
>
> ### https://pad.lv/1945053 - (New) [ubuntu-advantage-tools] - updating
> ubuntu 16.04 to 18.04 failed
>
> Pinged u-a-t folks.
>
>
> ### https://pad.lv/1945055 - (New) [mysql-8.0] - package
> mysql-server-8.0 8.0.26-0ubuntu0.20.04.3 failed to install/upgrade:
> o subprocesso instalado, do pacote mysql-server-8.0, o script
> post-installation retornou erro do status de saída 1
>
> Most likely a local configuration issue.
>
>
>
> Bugs tagged 'server-next' and not touched in 60 days
> Found 1 bugs
>
> ###https://pad.lv/1832182 - (Fix Committed) [apache2] - systemd unable
>to detect running apache if invoked via apache2ctl graceful

This one might be slightly more complex, I've updated [1] the case
and IMHO bryce who worked on it in the past needs to have a look
again to decide on next steps.

[1]: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1832182/comments/41

> This one got flagged, but it's been handled already.
>
>
> --
> Sergio
> GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam



-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2021-06-21)

[Robie Basak]

On Thu, Jul 01, 2021 at 05:09:28PM -0700, Bryce Harrington wrote:
> Robie, does this fix look like something the SRU team would accept?
> It's a new feature, but really is more a hardware-enablement thing.

Yes - this seems reasonable from a hardware enablement SRU perspective.


signature.asc
Description: PGP signature
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2021-06-21)

[Bryce Harrington]

On Mon, Jun 21, 2021 at 02:09:57PM -0400, Sergio Durigan Junior wrote:
> ### https://pad.lv/1864612 - (Triaged) [ipmitool] - requests ipmi-tool
> to include lasted patch for supporting quanta server
> 
> I don't know if there's anything worth doing on this one.  It's been
> marked as Triaged/Wishlist.  We could work on preparing an SRU for it
> (there is a fix available, apparently), but I don't think we have a
> scheduled upload for ipmitool in the horizon.

I've uploaded the fix to -proposed.

Robie, does this fix look like something the SRU team would accept?
It's a new feature, but really is more a hardware-enablement thing.

Bryce

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2021-03-15)

[Utkarsh Gupta]

Hi,

On Mon, Mar 15, 2021 at 9:50 PM Sergio Durigan Junior
 wrote:
> ### https://pad.lv/1909816 - (New) [asterisk] - asterisk spams console
> output to syslog due to systemd misconfiguration
>
> Valid, but seems low priority.  I marked it as such, set the status to
> Triaged, subscribed ubuntu-server and tagged it as bitesize.

Patch attached to the bug; forwarded to Debian (cf: #985314), and
X-Debbugs-Cc'ed the bug.


- u

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage Report (2020-11-02)

[Bryce Harrington]

On Wed, Nov 04, 2020 at 12:22:06PM -0500, Sergio Durigan Junior wrote:
> This is the (late) Monday triage report for 2020-11-02.
> 
> ustriage reported 12 bugs found.  These are the ones I had to work on:
> 
> ### https://pad.lv/1893543 - (New) [dovecot] - dovecot is not parsing
> the variables in dovecot-ldap.conf.ext correctly
> 
> The user reopened the bug (it had expired), but did not provide more
> info.  I read the message he sent to the dovecot users list, and
> apparently there was not progress there.  I marked the bug as Incomplete
> and asked the user whether he's got more insights to share with us.

Ah, I remember working on this a while back.  I saw that he was
attempting a rather atypical configuration that looked like it might be
pushing the envelope a bit on what dovecot supports (the documentation
is vague on if it is or isn't allowed), which is why I directed him
upstream.  I suspected it might be an unsupported feature that would
best be implemented there; and if it wasn't they could course correct
him.

From upstream's response, it looks like it's the former rather than the
latter.  They suggested some workarounds, but the reporter says he's
already doing one of them and is really more interested in having the
feature added.

https://dovecot.org/pipermail/dovecot/2020-September/119831.html

Unfortunately there's nothing we can feasibly do on our end towards
implementing that support for him.  Getting a patch SRU'd might also be
challenging since the setup requires LDAP and multiple domains; this is
one where we'd probably need the user to do the validation.

Bryce


> ### https://pad.lv/1901708 - *(Incomplete) [mysql-8.0] - package
> mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 failed to install/upgrade:
> installed mysql-server-8.0 package post-installation script
> subprocess returned error exit status 1
> 
> Sigh...  A bunch of people are commenting/opening these MySQL bugs
> against Focal.  It seems like the last mysql update really broke things,
> but I can't reproduce the problem here.  I tried one more time to set up
> a Focal container with very limited resources, but the upgrade
> succeeded.
> 
> 
> ### https://pad.lv/1901830 - (Confirmed) [mysql-8.0] - package
> mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 failed to install/upgrade:
> installed mysql-server-8.0 package post-installation script
> subprocess returned error exit status 1
> 
> Another person commented on the bug and said that they're having the
> same problem, but by looks of it (he posted the logs), it's a different
> issue, so I told him that.  For the reporter, I asked if he know whether
> the system was under high load during the upgrade process.  Yes, I'm at
> a loss here...  BTW, I think we can mark this as duplicate of 1901708 (I
> didn't do it because I want to see what Paride thinks first, since he
> started the investigation).
> 
> 
> ### https://pad.lv/1901995 - (Confirmed) [mysql-8.0] - package
> mysql-server-8.0 8.0.22-0ubuntu0.20.10.2 failed to install/upgrade:
> installed mysql-server-8.0 package post-installation script
> subprocess returned error exit status 1
> 
> One more that looks like 1901708.  I could not gather much info from the
> logs posted, so I asked a few more questions and marked the bug as
> Incomplete.  Eventually, if the user confirms that it is indeed the same
> bug, we can mark it as duplicate of 1901708.
> 
> Something interesting to note here is that, in this specific bug, the
> "Server upgrade" operation takes less than 5 minutes.  So yeah, maybe
> we're looking at the wrong place here.
> 
> 
> ### https://pad.lv/1902348 - (New) [mysql-8.0] - package
> mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 failed to install/upgrade:
> installed mysql-server-8.0 package pre-removal scrip$ subprocess
> returned error exit status 1
> 
> This is actually a different issue!  A sequence of operations to install
> MySQL/MariaDB rendered MySQL in a strange state.  I was able to
> reproduce it and marked the bug as Triaged.
>
> 
> Bugs in backlog and not touched in 180 days:
> 
> Found 3 bugs
> https://pad.lv/1633485 - (Triaged)[mysql-5.6]  - Backport login 
> throttling plugin to 5.6 and 5.7
> https://pad.lv/1828074 - (Triaged)[augeas] - Memory usage 
> issues with large Apache httpd configuration files
> https://pad.lv/1869848 - (Confirmed)  [libvirt]- libvirtd 
> virNetSocketReadWire:1811 : End of file while reading data: Input/output error
> 
> -- 
> Sergio
> GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEE6S/Qs2sU8fTY4OsvEG2hyMPLvxQFAl+i4z4ACgkQEG2hyMPL
> vxTOOA/9GipY9SZA/gDB9QP5flhknbtLrPlmEXOqF/10peEuGlrEXD+5eqkl+xoU
> /mGOult+SApAqj/fSQmVZzIxZzHS/AV/0yIhvwmuzK2HY5dKYVZdzrkfmcHxH5Jt
> BQPe11CnN0JVjyW4tr8qyTn062cLjN4mSN47PDt9S7dNUEBjS+9boReiMr9+AP4f
> 

Re: Monday Triage Report (2020-11-02)

[Robie Basak]

On Wed, Nov 04, 2020 at 12:22:06PM -0500, Sergio Durigan Junior wrote:
> Sigh...  A bunch of people are commenting/opening these MySQL bugs
> against Focal.  It seems like the last mysql update really broke things,
> but I can't reproduce the problem here.  I tried one more time to set up
> a Focal container with very limited resources, but the upgrade
> succeeded.

Without looking at the specifics here, usually it's not that an update
breaks things, but that it's common for users to have broken their own
MySQL installations in various different ways (usually these are
experiments rather than production). Then on an upgrade the maintainer
script fails when it tries to restart an already failing daemon and it
appears that the problem is the upgrade when that wasn't the cause.

My view on these is if people can provide specifics of where there
actually is a bug in our packaging, then we can fix it, but unless we
have that it's not worth wasting time on individual cases except to try
and detect a general pattern to find specific use cases that we can
actually fix. I'm not sure there are many left though; I suspect that in
most cases the steps users actually followed to end up with a failure
would not be considered to be supported (eg. installing from third party
repositories, customization hacks, and so on). I suspect quite a lot of
this is driven by broken third party instructions that users have
followed some time in the past.

> ### https://pad.lv/1902348 - (New) [mysql-8.0] - package
> mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 failed to install/upgrade:
> installed mysql-server-8.0 package pre-removal scrip$ subprocess
> returned error exit status 1
> 
> This is actually a different issue!  A sequence of operations to install
> MySQL/MariaDB rendered MySQL in a strange state.  I was able to
> reproduce it and marked the bug as Triaged.

This is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1490071 I
think?


signature.asc
Description: PGP signature
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage (2020-06-15) - Did by accident @paride, sorry

[Bryce Harrington]

On Mon, Jun 15, 2020 at 03:01:15PM -0300, Rafael David Tinoco wrote:
> On Mon, Jun 15, 2020 at 2:11 PM Bryce Harrington
>  wrote:
> >
> > On Mon, Jun 15, 2020 at 04:07:34AM -0300, Rafael David Tinoco wrote:
> > > https://pad.lv/1883090 -  (Confirmed) [apache2]- package
> > > apache2 2.4.41-4ubuntu3 failed to install/upgrade: el subproceso
> > > instalado paquete apache2 script post-installation devolvió el código
> > > de salida de error 1
> > >
> > > > similar upgrade issues have been seen with apache2 and its mods
> > > > asked @bryce if he hadn't worked on this (iirc) recently
> > > > it seems that deferred pkg configuration (after deps) does not work
> >
> > That one was with mod-php during a system upgrade when mod-php was
> > already installed, this one is mod-fcgid during initial apache
> > installation when mod-fcgid is not yet installed.
> >
> > I tried to reproduce the bug in lxc but the installation worked ok for
> > me.  Were you able to reproduce it?
> 
> Nope, I haven't tried it. Just remembered you worked in something
> similar. If it is not the same, then let's just keep it under our
> queue then.

mod-php actually is provided by the php7.4 package (the aformentioned
bug needed a code fix to a postinst script in php7.4 -- so an entirely
separate codepath).  

> Perhaps we can address those upgrade issues during next merge,
> altogether...
> 
> sounds good ?

mod-fcgid looks like it comes from the libapache2-mod-fcgid package (not
from apache2), and that package is just sync'd from Debian.

I don't spot a matching bug for this issue in Debian, but looking at the
ubuntu bugs for this source package, there's about half a dozen relating
to installation issues with that package.  LP: #1266400 appears to be
caused by dir perm's, the other bugs aren't analyzed yet but wouldn't
surprise me if some are dupes.  It makes me suspect that whatever this
issue is, it might be a longstanding but corner case issue.

Anyway, I think your call to keep it in our subscription queue for now
is good.

Bryce

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage (2020-06-15) - Did by accident @paride, sorry

[Rafael David Tinoco]

On Mon, Jun 15, 2020 at 2:11 PM Bryce Harrington
 wrote:
>
> On Mon, Jun 15, 2020 at 04:07:34AM -0300, Rafael David Tinoco wrote:
> > https://pad.lv/1883090 -  (Confirmed) [apache2]- package
> > apache2 2.4.41-4ubuntu3 failed to install/upgrade: el subproceso
> > instalado paquete apache2 script post-installation devolvió el código
> > de salida de error 1
> >
> > > similar upgrade issues have been seen with apache2 and its mods
> > > asked @bryce if he hadn't worked on this (iirc) recently
> > > it seems that deferred pkg configuration (after deps) does not work
>
> That one was with mod-php during a system upgrade when mod-php was
> already installed, this one is mod-fcgid during initial apache
> installation when mod-fcgid is not yet installed.
>
> I tried to reproduce the bug in lxc but the installation worked ok for
> me.  Were you able to reproduce it?

Nope, I haven't tried it. Just remembered you worked in something
similar. If it is not the same, then let's just keep it under our
queue then. Perhaps we can address those upgrade issues during next
merge, altogether...

sounds good ?

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage (2020-06-15) - Did by accident @paride, sorry

[Bryce Harrington]

On Mon, Jun 15, 2020 at 04:07:34AM -0300, Rafael David Tinoco wrote:
> https://pad.lv/1883090 -  (Confirmed) [apache2]- package
> apache2 2.4.41-4ubuntu3 failed to install/upgrade: el subproceso
> instalado paquete apache2 script post-installation devolvió el código
> de salida de error 1
> 
> > similar upgrade issues have been seen with apache2 and its mods
> > asked @bryce if he hadn't worked on this (iirc) recently
> > it seems that deferred pkg configuration (after deps) does not work

That one was with mod-php during a system upgrade when mod-php was
already installed, this one is mod-fcgid during initial apache
installation when mod-fcgid is not yet installed.

I tried to reproduce the bug in lxc but the installation worked ok for
me.  Were you able to reproduce it?

Bryce

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage (2020-06-15) - Did by accident @paride, sorry

[Rafael David Tinoco]

> >
> > https://pad.lv/1785383 - (Triaged)[dnsmasq]- missing
> > EDNS0 record confuses systemd-resolved
> > also:  - (New)[systemd]- missing
> > EDNS0 record confuses systemd-resolved
> >
> > > @ddstreet seems to have caught this to himself, cc'ing him
>
> yes, this is an unfortunate loong running bug that is due to a
> patch to systemd that we carry, that isn't upstream.  It will require
> me (or someone) being able to go to a Starbucks to test with their
> wifi, so I (or someone) can create a proper patch to workaround their
> broken wifi captive portal, that we can then get merged upstream and
> drop the problematic patch we carry.  That's been made difficult by
> COVID-19, of course, but I do still want to try to get to this
> sometime this summer.

Oh, a bug that has Starbucks as a requirement! Finally! It is also in
our queue and tagged as server-next (higher priority).

Thanks for the reply!

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Triage (2020-06-15) - Did by accident @paride, sorry

[Dan Streetman]

On Mon, Jun 15, 2020 at 3:08 AM Rafael David Tinoco
 wrote:
>
> Bugs last updated between 2020-06-12 (Friday) and 2020-06-14 (Sunday) 
> inclusive
> Date range identified as: "Monday triage"
> Found 20 bugs
>
> https://pad.lv/1817955 -  (Confirmed) [krb5]   - Getting
> new DN is out of the realm subtree error on adding principal
>
> > subscribed ebarretto (author of the security fix that caused the regression)
> > subscribed ubuntu-server
> > triaged for trusty, fix released for groovy
>
> https://pad.lv/1882527 -  (Confirmed) [mysql-8.0]  - mysql
> timeoutsec results in killing mysql process
>
> > triaged for all supported releases
> > tagged as server-next and high prio for groovy
> > it shall be an easy fix/sru: disable TimeoutSec from systemd service unit 
> > (upstreamed already)
>
> https://pad.lv/1882791 -  (Confirmed) [mysql-8.0]  - package
> mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade:
> installed mysql-server-8.0 package post-installation script subprocess
> returned error exit status 1
>
> > incomplete (upgrade)
> > could not stop previous instance issue (very frequent)
>
> https://pad.lv/1883090 -  (Confirmed) [apache2]- package
> apache2 2.4.41-4ubuntu3 failed to install/upgrade: el subproceso
> instalado paquete apache2 script post-installation devolvió el código
> de salida de error 1
>
> > similar upgrade issues have been seen with apache2 and its mods
> > asked @bryce if he hadn't worked on this (iirc) recently
> > it seems that deferred pkg configuration (after deps) does not work
>
> https://pad.lv/1883307 -  (New)   [mysql-8.0]  - package
> mysql-server-8.0 (not installed) failed to install/upgrade: el
> subproceso nuevo paquete mysql-server-8.0 script pre-installation
> devolvió el código de salida de error 1
>
> > incomplete, weird error about /etc/mysql/FROZEN
> > asked more information
>
> https://pad.lv/1883320 -  (New)   [sosreport]  - [kvm]
> change check_enabled to /dev/kvm
>
> > sosreport and @slashd is on it, nothing on our side
>
> https://pad.lv/1883398 -  (New)   [qemu]   - USB
> serial device passtrough causes qemu to segfault and kill the VM
>
> > asked for detailed reproducer or core file
> > subscribed ubuntu-virt and @cpaelzer
> > stated as incomplete until then
>
> https://pad.lv/1883413 -  (New)   [bind9]  - bind9
> /var/cache/bind rights not set properly
>
> > not a bug, end user wanted to document his finding more than anything
> > flagged as opinion and subscribed ubuntu-server
>
> ---
> Bugs tagged 'server-next' and not touched in 60 days
> Found 2 bugs
>
> https://pad.lv/1785383 - (Triaged)[dnsmasq]- missing
> EDNS0 record confuses systemd-resolved
> also:  - (New)[systemd]- missing
> EDNS0 record confuses systemd-resolved
>
> > @ddstreet seems to have caught this to himself, cc'ing him

yes, this is an unfortunate loong running bug that is due to a
patch to systemd that we carry, that isn't upstream.  It will require
me (or someone) being able to go to a Starbucks to test with their
wifi, so I (or someone) can create a proper patch to workaround their
broken wifi captive portal, that we can then get merged upstream and
drop the problematic patch we carry.  That's been made difficult by
COVID-19, of course, but I do still want to try to get to this
sometime this summer.

>
> ---
> Bugs in backlog and not touched in 180 days
> Found 0 bugs

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam