This is a tracking bug for Change: DNS Over TLS For more details, see: https://fedoraproject.org/wiki/Changes/DNS_Over_TLS Fedora will attempt to use DNS over TLS (DoT) if supported by configured DNS servers.
Today we reached the Completion deadline (testable) milestone in the Fedora schedule. All approved changes should be in a testable state. If you change is testable, please indicate this by setting the status to MODIFIED. If you need to defer the change to Fedora 35 or withdraw the change entirely, please indicate this in a comment and NEEDINFO bcotton. The 100% code complete deadline is Tuesday 23 February. By that date, your change should be fully implemented and the tracking bug set to ON_QA. For other Fedora 34 milestones, see https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
Uh, looks like we forgot to enable this? I see it's still disabled by default upstream, and we do not change that in Fedora. All we need to do is change a build flag, so should be trivial to enable.
Hi Ben, Zbigniew thinks it's best for this change to slip to F35. I've attempted to retarget the change proposal page accordingly. Please let me know if I missed anything, thanks!
No need to change the category. I'll update the other trackers, thanks!
Today is the "Code complete (testable)" deadline in the Fedora Linux 35 release schedule: https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html If this Change is complete enough to be tested, please indicate this by setting this bug to the MODIFIED status. (If it is 100% complete, you can set it to ON_QA). If you wish to defer this Change to Fedora Linux 36, please needinfo bcotton.
This is enabled since systemd-249.2-1.fc35.
I think we're 100% complete?
Yeah.
Note we have pulled the contingency parachute on this one due to bug #2006393 . I have just sent a build which disables dns-over-tls again and will submit it as an update shortly. Not sure what the protocol is for this situation, for now returning the bug to ASSIGNED.
I've retargeted the change proposal on Fedora wiki to F36 and resubmitted it to the change wrangler.
Updated the tracking bug, too. :-)
This bug appears to have been reported against 'rawhide' during the Fedora Linux 36 development cycle. Changing version to 36.
Today we reached the Code Complete (testable) milestone in the F36 schedule: https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html All code for this change should be complete enough for testing. You can indicate this by setting the bug status to MODIFIED. (If the code is fully complete, you can go ahead and set it to ON_QA.) If you need to defer this Change to F37, please needinfo bcotton.
We have reached the 'Change complete (100% complete) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be fully complete. Indicate this by setting this tracking bug to ON_QA. If you need to defer this Change to a subsequent release, please needinfo me.
Well the change is complete, but we have unresolved bugs and have not yet decided whether or not to roll back.
Setting to ON_QA per FESCo: https://meetbot.fedoraproject.org/teams/fesco/fesco.2022-03-01-18.03.log.html#l-100 If this Change needs to be rolled back, please needinfo me and I'll make the appropriate tracker updates.
Unfortunately I think it's time to activate the contingency plan and switch back to -Ddns-over-tls=no. Upstream needs more time to sort through the issues.
Can we do that for Beta if we're going to do it? We are going to be no-go tomorrow, so there's a few days to get it in.
That's up to Zbigniew, but honestly I don't think it's urgent enough to require a freeze exception.
(In reply to Michael Catanzaro from comment #17) > Unfortunately I think it's time to activate the contingency plan and switch > back to -Ddns-over-tls=no. Upstream needs more time to sort through the > issues. Ack. Let me know when the switch is made and I'll shuffle the paperwork appropriately.
(In reply to Adam Williamson from comment #18) > Can we do that for Beta if we're going to do it? We are going to be no-go > tomorrow, so there's a few days to get it in. I don't have permission to touch the systemd package, but I've created merge requests: https://src.fedoraproject.org/rpms/systemd/pull-request/74 https://src.fedoraproject.org/rpms/systemd/pull-request/75
Filed https://bugzilla.redhat.com/show_bug.cgi?id=2064089 as a proposed FE.
FEDORA-2022-1dd97eaa2b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1dd97eaa2b
Zbigniew, shall we drop this change proposal? It seems to have failed. Clearly we cannot enable opportunistic mode without more work in systemd-resolved, which has not been prioritized.
Hi Ben, is it possible to withdraw this change proposal?
Sure thing. I'll take care of the paperwork.