sudo dnf upgrade --advisory=FEDORA-2021-a3ab421a63
This update has been submitted for testing by harald.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
This update leads to a broken initramfs
Workaround for me is to: echo "omit_dracutmodules+=bluetooth" | sudo tee /etc/dracut.conf.d/omit_bt.conf
echo "omit_dracutmodules+=bluetooth" | sudo tee /etc/dracut.conf.d/omit_bt.conf
(cc @cserpentis )
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This does not fix the bluetooth-related bug that generates unbootable images introduced by dracut 054.
@luminoso @bcdonadio The 054 version is already stable, and so it doesn't make sense to downvote 055 just because it doesn't fix the bug. It fixes other bugs, so it's an improvement, thumbs up. Thumbs down is only applicable is this very update introduces some regression over the previous stable version.
I ran dracut -f and can still boot with this update, so +1 from me.
@kparal Ok, fair point. I think the way the karma question is worded leads to a ambiguous interpretation given that the logic actually gates the update instead of providing just a general sense of "it is working for you or not". Changing my vote, since it works on my other machine at least.
This update can be pushed to stable now if the maintainer wishes
Should be pushed stable, due to missing fsck utils. Mounting and using dirty sysroot is just severe. I've opened a bug, that might be linked here and closed when stable. Can confirm, that it's fixed.
This update is still broken (regressed in 54).
https://bugzilla.redhat.com/show_bug.cgi?id=1965585 is still broken by 55; see also https://bugzilla.redhat.com/show_bug.cgi?id=1968699#c2 for further symptoms.
Dowgrading to dracut 53 is the only working solution at this time.
@ciperboy See my comment above on why you shouldn't give -1 karma here just because it doesn't fix something, when it fixes other things.
@kparal the very first question is "Karma: is the update generally functional" -- I replied as much, as it is not functional and is broken.
When I first posted, there were nearly 50% failed OpenQA tests. This is not a sign of a stable update that should be pushed out to users; negative karma is the right answer in either case, if nothing else, so the maintainer is aware. The failing OpenQA appear to have been fixed since.
In general, I agree if it was a random library with fewer users and infrequent releases. But this is a critpath core system package that has seen four updates (just to F34 alone!) in three weeks, causing regressions for users. And I do understand, mistakes happen as a packager. I've made them myself. But perhaps we should take the users (myself included) up on their offer of debugging, and make a single, solid update rather than continuing to push half-broken updates every couple of weeks. :-)
Additionally... How do I, as someone who has installed this advisory and tested it, know whether it isn't broken in some other way, obscured by the symptoms of the above BZ? Just curious. :-) Should users who aren't happy with the current version not test future advisories unless it and all intermediate versions fully work for them?
My 2c., but there is value in the "Is this update generally functional?" question independent of the test cases and independent of current/previous version. Not everyone will have updated from the same immediate version prior, especially at this pace of updates. At that point, it would become a value call to the maintainer as to whether or not to push, and if as a maintainer, you wish to ignore the negative karma, that is fine. But telling users not to use this avenue of feedback, IMO, is wrong.
Perhaps devel@ would be a better place for this discussion. :-)
@cipherboy the reported 'failed' openQA tests weren't actually test failures, they were a weird greenwave blip (it was reporting 'missing' test results that weren't actually missing, for all updates, not just this one). openQA does not test anything to do with bluetooth, so it did not encounter this bug. Neither the 054 update nor this one actually had any failed openQA tests.
The question is just the best wording we could come up with for casual human readers; really that is the karma vote. The other things don't feed into the karma number at all. Your response to the "generally functional" question is a +1 or -1 on this specific update. As @kparal says, there is no benefit to -1ing an update because it doesn't fix something that is already broken in stable.
adamwill edited this update.
Karma has been reset.
This update has been submitted for testing by adamwill.
I've updated the update to a build that should never include the bluetooth module by default (you can still explicitly include it, for testing purposes). This is a workaround until upstream can figure out and fix the bug properly. Please let me know if it doesn't behave as expected. Thanks!
Thank you! dracut-055-2.fc34 makes my system bootable again without any manual workarounds :-)
It looks like the bluetooth issue is now fixed.
F34 + bluetooth keyboard & mouse: with new dracut and initramfs rebuild everything worked like a charm.
For newbies (like me). Boot in top kernel. If failing, wait for timeout, open second pty with ctrl+alt+f3
dracut --version # should show version 054 or lower, if higher than 055-2 then this won't help for bluetooth issue
dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a3ab421a63
dracut --version # shows 055-2
uname -r # verify current kernel booted from
grubby --info $(grubby --default-kernel) # are we booted from the default kernel?
# backup initramfs of index=0
cp /boot/initramfs-5.12.10-300.fc34.x86_64.img /boot/initramfs-5.12.10-300-withbt.fc34.x86_64.img
dracut # should show an error that --force is needed and it will overwrite the initramfs copied above
dracut --force # if booted in latest kernel
I was able to boot kernel-core-5.12.11-300.fc34.x86_64
works for me
This update has been submitted for stable by adamwill.
This update has been pushed to stable.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.