Proposed change to rendering of release schedule ics file
by Ben Cotton
Hi everyone,
I want to get feedback before I make a change to how Fedora Linux
schedules are generated. As reported in schedule#91[1], the current
ics files include very long tasks that aren't particularly useful. I
have a plan for how to address that, but first I want to check that it
won't impact how people currently use the ics files.
If you're using the Fedora Linux schedule ics files, please see the
details in the Pagure issue[2]. If this will affect how you or your
team use those files, comment in the issue before 13 February. Note
that this will not change how the html or json versions are produced.
[1] https://pagure.io/fedora-pgm/schedule/issue/91
[2] https://pagure.io/fedora-pgm/schedule/issue/91#comment-838492
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
1 month, 2 weeks
Boot issue, probably with grub and maybe mdraid
by Bruno Wolff III
Today one of three machines failed to boot 6.2.0-0.rc4. The machine that
failed had not been rebooted in a week and now won't boot any kernel and
it appears grub is aborting with a pointer out of range error. All three
machines use ext4 and luks, but only the failing machine uses mdraid.
I haven't recovered the failing machine yet, but plan to downgrade grub
tomorrow and hope that confirms a grub bug by allowing it to boot. If
so, I'll file a bug report.
I'm wondering if anyone else saw this and/or if they think there might be
a different issue I should be looking for?
1 month, 2 weeks
Delayed openQA test execution
by Adam Williamson
Hey folks! Wanted to send a note out for any maintainers who may be
waiting on openQA test results for critical path updates etc. Tests are
currently taking much longer than usual to be completed because there's
a large backlog. The Rawhide mass rebuild, plus the three critical bugs
(python-ptyprocess, systemd, and mesa) that I posted about yesterday,
caused 2-3 days' worth of Rawhide update tests to fail. After finally
sorting out those problems enough that the tests now pass, I
rescheduled that whole backlog, which turned out to be over 2000 tests.
The system is working its way through the backlog but it'll take a
while (I expect it should be clear by end of day today or so, it
depends a bit on how many updates are created in the mean time), and
until that gets done, it may take much longer for the tests for any
given update to be completed after the update is created.
I do apologize for this; with hindsight it might've been better to try
and hack up a way to reduce the priority on the backlogged Rawhide
update tests so tests for stable release updates ran first, but I
didn't think of that yesterday.
If there are any urgent security or critical bug fix updates for stable
releases which are waiting on testing and really need it run ASAP, let
me know and I can manually bump the priority of those tests so they run
sooner.
Thanks folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 month, 3 weeks
Re: Some heads-ups for Rawhide users: python3-ptyprocess and
systemd issues
by Adam Williamson
On Thu, 2023-01-26 at 12:41 +0100, Florian Weimer wrote:
> * Adam Williamson:
>
> > 6 (__libc_message.cold+0x5) [0x7fbae3c2560f]
> > Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 6: /lib64/libc.so.6 (malloc_printerr+0x15) [0x7fbae3c96a05]
> > Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 7: /lib64/libc.so.6 (_int_free+0x9e5) [0x7fbae3c98de5]
> > Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 8: /lib64/libc.so.6 (__libc_free+0x7e) [0x7fbae3c9b42e]
> > Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 9: /usr/lib64/dri/zink_dri.so (__driDriverGetExtensions_zink+0x9e70) [0x7fbad82b8180]
> > Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 10: /lib64/libgbm.so.1 (gbm_format_get_name+0xe81) [0x7fbae3229361]
> > Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 11: /lib64/libgbm.so.1 (gbm_format_get_name+0x1018) [0x7fbae32294f8]
> > Jan 25 13:38:47 fedora /usr/libexec/gdm-x-session[1040]: (EE) 12: /lib64/libgbm.so.1 (gbm_format_get_name+0x121a) [0x7fbae32296fa]
>
> I saw this during the latest glibc update, but given that the update
> wasn't tested in isolation, I waived it through because the update
> addresses the known sprintf issue.
>
> I'm not aware of anything in glibc this might have caused this. The
> crashes related to -D_FORTIFY_SOURCE=3 look different (they try to crash
> before causing heap corruption!), and it's not the sprintf assertion
> failure in __printf_buffer_as_file_commit, either.
>
No, it's definitely mesa that causes it - I verified that with manual
local testing, updating only mesa causes the bug to start happening,
downgrading it makes it go away. This is now being tracked/investigated
as https://bugzilla.redhat.com/show_bug.cgi?id=2164667 .
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 month, 3 weeks
Some heads-ups for Rawhide users: python3-ptyprocess and systemd
issues
by Adam Williamson
Hey folks! Just wanted to send out a heads-up for Rawhide users about
some issues that have shown up in openQA testing.
First, you may have found that trying to update to today's Rawhide
fails like this:
Error: Transaction test error:
file /usr/lib/python3.11/site-packages/ptyprocess-0.7.0-py3.11.egg-info from install of python3-ptyprocess-0.7.0-2.fc38.noarch conflicts with file from package python3-ptyprocess-0.7.0-1.fc38.noarch
That's https://bugzilla.redhat.com/show_bug.cgi?id=2164207 , we figured
out the problem (thanks to Panu for getting to the root cause of it)
and it is fixed in python-ptyprocess-0.7.0-3.fc38 , which should be in
the next Rawhide compose. If you really can't wait you can update
directly to that version
from https://koji.fedoraproject.org/koji/buildinfo?buildID=2138649 ,
but you'd better watch out for issue #2...
The second issue is that systems that update to systemd-253~rc1-1.fc38
seem to get stuck on boot. With Plymouth enabled you just see the
splash screen. With it disabled (or by pressing esc) it seems to be
stuck at "Stopped initrd-switch-root.service - Switch Root.". I'm still
looking into this one, but it's happened to a lot of openQA tests and I
was able to confirm it first try in a local VM, by installing from the
20230123.n.0 compose then updating systemd and rebooting. Fresh
installs with the newer systemd seem to be OK, at least most openQA
tests for the new compose passed - it seems to be only updating an
existing install that has the problem, at least so far.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 month, 3 weeks
Fwd: [Test-Announce] Heads up: testing requested for significant
PackageKit update
by Kamil Paral
---------- Forwarded message ---------
From: Adam Williamson <adamwill(a)fedoraproject.org>
Date: Tue, Jan 24, 2023 at 1:29 AM
Subject: [Test-Announce] Heads up: testing requested for significant
PackageKit update
To: <test-announce(a)lists.fedoraproject.org>
Hey folks!
The desktop team kindly let us know that there's a fairly significant
PackageKit update coming. It's been built for Rawhide today (so will be
in tomorrow's compose) and is now in updates-testing for F37:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-6c1c40d160
what it does is re-enable a feature where the PackageKit daemon doesn't
run forever as it does now, but shuts down after an inactivity timeout.
This should save a decent amount of RAM, as the daemon tends often to
consume 400M+ of the stuff.
This feature has been turned on and off and on and off again a few
times before because it was found to cause problems. This time, a few
folks have done some diligent work trying to ensure all the previously-
encountered problems were solved, but of course it's *possible* they
missed something, or there are some other problems that folks weren't
aware of.
So it'd be great if as many folks as possible can install this update
and check how it goes. In the past, problems have tended to arise when
you mix operations between dnf and PackageKit-based apps like GNOME
Software, so please pay attention to those kinds of cases - if you
habitually do some stuff with dnf at the command line and some stuff in
Software, keep an eye out for new problems or oddities. Also look out
for incorrect or non-functional update notifications from GNOME,
especially if you e.g. update via DNF but then get a notification from
GNOME for the same updates.
There's some more background reading here:
https://github.com/PackageKit/PackageKit/pull/578
for folks who are interested.
The update for F37 has karma auto-push disabled and time-based auto-
push set to 21 days, so we have plenty of time to find any major
problems with it - don't worry about it being rushed into stable before
we're sure it's OK.
Thanks everyone!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 month, 4 weeks
Last known Good for Rawhide (Server Edition) -- Not Good
by Onyeibo Oku
Good Morning,
I'd like to bring something to attention. I just downloaded Server
Boot Media (Netinstall) from:
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-2022120...
I made a USB boot disk out of that and it failed to boot.
Here is what I get after choosing to install at the GRUB Menu:
error: ../../grub-core/fs/fshelp.c:257:file '/images/pxeboot/vmlinuz'
not found
error: ../../grub-core/loader/i386/efi/linux.c:258:you need to load the
kernel first.
Press any key to continue ...
The ISO was registered as "last known good". This can't be good.
Which one really works?
2 months, 1 week
Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
by Ben Cotton
On Tue, Jan 10, 2023 at 5:35 AM <bcotton(a)redhat.com> wrote:
>
> You are kindly invited to the meeting:
> Prioritized bugs and issues on 2023-01-11 from 10:00:00 to 11:00:00 America/Indiana/Indianapolis
> At fedora-meeting-1(a)irc.libera.chat
>
> More information available at: https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/
There are no nominated prioritized bugs, so I'm cancelling this week's
meeting. I follow up with the currently accepted bugs out of band. The
next meeting is scheduled for 25 January.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 months, 1 week
