Also remove existing file when creating /etc/resolv.conf symlink upon installation (#1873856 again).
No need to log out or reboot, since this change affects only new installations.
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-2020-8c3c5881b2
Please login 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 has been submitted for testing by zbyszek.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This cannot be tested until it goes stable, so fake +1 karma to facilitate testing.
This update's test gating status has been changed to 'ignored'.
Well, openQA tested it far enough that it's not happy: mock does not like
/etc/resolv.conf
not existing, it seems.More specifically, I think
mock --old-chroot
- which is the same asmock --isolation=simple
- doesn't like it.Filed https://bugzilla.redhat.com/show_bug.cgi?id=1878924 to track the problem for now.
Same bug seems to have broken today's Rawhide compose. We do not want F33 composes broken the same way, so -1 for now.
This update has been pushed to testing.
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.
We think the mock issue is fixed now with a new mock deployed to the builders...we'll see how the next Rawhide compose goes, that should help figure out how safe it'd be to push this for F33.
OK, the mock issue is fixed and a Rawhide compose got through. Switching my vote to +1 and we'll hope it works.
This update can be pushed to stable now if the maintainer wishes
let's just push it and see what happens.
This update has been submitted for stable by adamwill.
works
This update has been pushed to stable.