Fixes to the issues listed and various other small buglets.
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-2021-1c1a870ceb
Please login to add feedback.
0 | 5 | Test Case base service manipulation |
0 | 5 | Test Case base services start |
0 | 5 | 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 update's test gating status has been changed to 'ignored'.
This seems to also fix #1941335
zbyszek edited this update.
Yeah, it has a patch for that. I forgot to include it in notes though.
This update has been submitted for stable by bodhi.
I revoked this because of the openQA results. It seems to have broken name resolution really badly in openQA. All the failures failed on DNS lookups.
Just to make sure, I am -ve karma it
While I was able to test the base test cases, and the fix for BZ#1941335, there seems to be some odd networking issue with this new version for me: while I'm able to
dig
domains just fine, there are a lot of domains that I'm not able to actually ping.Oddly I am able to ping google.com and bodhi.fedoraproject.org and visit them in a browser, but I'm not able to visit bugzilla.redhat.com, duckduckgo.com, opensource.com, bbc.co.uk.
I'm running Silverblue, and rolling back and forth between the version with this change applied and the one without it (which has
systemd-246.10-1.fc33.x86_64
), this version does seem to have that issue every time.Here's
dig @127.0.0.53
output for a name that doesn't work (www.google.com), then one that does (fedoraproject.org):Here's
resolvectl query
output for the same two:Also, oddly,
ping 1.1.1.1
works fine butdig @1.1.1.1 anyname
fails with "connection timed out; no servers could be reached".zbyszek edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by zbyszek.
Apologies for the bad version. Please test again. The diff is the first five commits on https://github.com/systemd/systemd-stable/commits/v246-stable.
@zbyszek given the recent general experiences, wouldn't it be sensible to disable autopush for this and future systemd updates, or at least set the threshold higher than +3?
The bad version here was extremely close to going stable and breaking networking for most of our user base, which would've done huge damage to both Fedora's and systemd's reputations.
I've tested that the new build fixes BZ#1941335 and the base test cases pass, and I don't experience any networking issues with this one.
I can verify that this fixes BZ#1941335 in the Europe/Dublin time zone. I'm not leaving overall karma to keep this from getting autopushed.
I did notice that this also fixes the networking errors that I belatedly saw with the previous build.
Seems ok here. No odd networking issues seen.
zbyszek edited this update.
Yes, that's reasonable. I disabled autokarma now.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
This update has been submitted for stable by zbyszek.
zbyszek edited this update.
This update has been pushed to stable.