DescriptionAdam Williamson
2021-04-08 20:23:49 UTC
systemd-resolved has a caching feature, which is specifically listed as one of the "Benefits to Fedora" in the Change:
https://fedoraproject.org/wiki/Changes/systemd-resolved#Caching
however, it's currently disabled to workaround several significant bugs we previously encountered with it turned on. We believe those bugs have been resolved, and there is a pending update with positive karma and clean openQA results that turns the caching back on:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-043d75eee9
but we just missed the freeze date with it, so I'm filing this and proposing it as an FE to propose we fix this for release.
It's not really a showstopper or anything. We can release this way and everything will work, we just miss a performance improvement. If it doesn't go out as an FE it can go as a 0-day update; the impact will be caching will be disabled in environments produced during the compose (lives, initial deployments of lives and disk images, the installer environment).
Comment 1Fedora Update System
2021-04-08 20:24:31 UTC
Comment 2FrantiĊĦek Zatloukal
2021-04-12 17:45:29 UTC
Discussed during the 2021-04-12 blocker review meeting: [1]
The decision to classify this bug as an AcceptedFreezeException was made:
"So far there's no indication that anyone's had name resolution issues with this, so we're hopeful it finally solves all the major problems. we do want the feature enabled for release as it's a major part of the change."
[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2021-04-12/f34-blocker-review.2021-04-12-16.02.log.txt
Comment 3Fedora Update System
2021-04-13 01:34:05 UTC
FEDORA-2021-043d75eee9 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.