New version of systemd + dracut with patches to support it.
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-2023-f631207330Please log in to add feedback.
| 0 | 0 | Test Case base service manipulation |
| 0 | 0 | Test Case base services start |
| 0 | 0 | Test Case base shutdown/reboot |
This update's test gating status has been changed to 'waiting'.
This update has obsoleted systemd-255~rc1-3.fc40, and has inherited its bugs and notes.
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'.
There still seem to be real issues with this update, but I'm on vacation and don't have time to investigate them. Briefly, the problems are that reboot from GNOME Software after doing a system update does not seem to work (that's https://openqa.fedoraproject.org/tests/2255717 ) and transition from gnome-initial-setup to a logged-in desktop after install of Workstation or Silverblue does not work, leaving the user at an unusable screen (the other three failures, e.g. https://openqa.fedoraproject.org/tests/2255743 ). You can find logs for each failure on the Logs & Assets tab - the file ending in var_log.tar.gz is a tarball of the whole of /var/log , so you can examine the journal files from there. Otherwise I'll be back to look into it on Monday (or will do it sooner if I get a bit of spare time from my spare time...)
I have run the first failure again and the test failed on rebooting in the following way: When it clicked on the "Restart" button, then the confirmation dialogue with "Restart and Install" appeared for a very short time, less than a second and then it disappeared, while openQA is still waiting for that confimation button to be clicked. I have checked the logs from the previous runs, but I could not find anything that would clearly tell me what the problems clearly was. I mean, there are some failures in journactl, but they all happened before the computer got updated with the advisory and restarted, after the restart when the problem happens, nothing really striking is to be seen.
I can surely help with obtaining the logs from the runs if @zbyszek wants to explore them.
For the first failure, there is a following error in user1000.journal file:
Could this indicate the crash of the confirmation box?
For the second case, the journal does not report any serious error, so this is even more tricky.
@zbyszek said he was gonna edit this update with patches from upstream at some point, so I guess we wait for that.
zbyszek edited this update.
New build(s):
Removed build(s):
Karma has been reset.
I'm not sure if any of the changes we made can help with those failures in QA. Let's see.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
Two tests are still faiing. One is 404 and the other doesn't seem to make much sense:
Undeclared file conflicts: dracut-059-16.fc40.i686 provides /usr/share/doc/dracut/dracut.html which is also provided by dracut-059-16.fc40.x86_64 dracut-059-16.fc40.i686 provides /usr/share/man/man1/lsinitrd.1.gz which is also provided by dracut-059-16.fc40.x86_64 ...
And
update.realm_join_cockpitis shown as running since 2 days ago, but the linked page saysResult: passed, finished a day ago (31:36 minutes). I'll try to waive it.This update's test gating status has been changed to 'passed'.
This update cannot be pushed to stable. These builds dracut-059-16.fc40 have a more recent build in koji's f40 tag.
Looks like the result of the realmd_join_cockpit test wasn't reported for some reason; possibly the consumer missed a message. However, as per above, you can't push this because FEDORA-2023-32cf2341a6 already went stable. if you edit this update and remove the dracut build from it, it will retrigger the tests and the update will be pushable if they pass. @zbyszek
zbyszek edited this update.
Removed build(s):
Karma has been reset.
This update has been submitted for stable by bodhi
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'.
huhh. that's an odd little sequence of events above. i need to see if bodhi has a bug there somewhere...
Seems this update broke a lot of testing in Fedora CI:
https://pagure.io/fedora-ci/general/issue/447
It would be good to start gating these critical updated to prevent that in the future. The installability failed, we should make it gating.
@adamwill were the results delivered too late here? Maybe that was the problem?