#52 1867830 can't connect using mDNS addressing when systemd-resolved is running
Closed 3 years ago by blockerbot. Opened 3 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1867830

Current vote summary

  • Accepted BetaFE (+1, 0, -0)

Commented but haven't voted yet: coremodule

The votes have been last counted at 2020-08-31 17:27 UTC and the last processed comment was #comment-674644

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review


This is somewhat risky, because the fix (and we don't seem to know how exactly the fix should look like, still) might introduce some networking regressions. At the same time, broken mDNS is very inconvenient and it's better to push the changes to Beta rather than post-Beta, I believe.

BetaFE +1

Discussed during the 2020-08-31 blocker review meeting: [0]

AGREED AcceptedBetaFE The decision to classify this bug as an "AcceptedFreezeException" was made as it is a noticeable issue that cannot be fixed with an update.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-08-31/f33-blocker-review.2020-08-31-16.00.txt

The following votes have been closed:

  • Accepted BetaFE (+1, 0, -0)

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

3 years ago

Release F33 is no longer tracked by BlockerBugs, closing this ticket.

Login to comment on this ticket.

Metadata