Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2025-e8a71b6caf
Please log in to add feedback.
| 0 | 0 | Test Case firefox addons |
| 0 | 2 | Test Case firefox browse |
| 0 | 2 | Test Case firefox media |
| 0 | 2 | Test Case firefox screenshot |
This update has been submitted for testing by stransky.
This update's test gating status has been changed to 'waiting'.
Looks fine in 40.
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 'failed'.
So there's something a bit odd going on here. There's a test where we go to the Updates page of Cockpit. If it's not immediately visible in the left bar - which it always isn't, these days - we do this by clicking on the magnifying glass next to the search box, then pressing the 'up' key. This should scroll the left bar to the bottom and make Updates visible. On the tests of the F41 and F42 134.0 updates, it did this no problem. On this update, it's failed twice in prod so far; on staging it failed once but worked on the auto-retry.
However, I do see that the same thing happened on one Rawhide nightly test since this went stable for Rawhide - this one. So it's not only happening on 40, but either we've been very 'lucky' with F40 tests or it's happening more often with F40 tests.
Since this update has 'high' security fixes, I'll rerun the F40 test till it passes on prod and let the update go through, but it would be good to figure out what's going on here. I'll also see if I can work out a workaround for the test (maybe pressing up twice will be enough).
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by bodhi.
This update has been pushed to stable.