Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1863041
Commented but haven't voted yet: adamwill, lruzicka
The votes have been last counted at 2020-09-20 00:28 UTC and the last processed comment was #comment-687246
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review
AGREED AcceptedBetaFE See bug for more info
The following votes have been closed:
From https://bugzilla.redhat.com//show_bug.cgi?id=1863041#c4 :
The decision to delay the classification of this as a blocker bug was made as this bug brings up an inadequacy of the criteria: we don't have explicit network or VPN criteria, and it'd be too much of a stretch to crowbar this into any existing criterion. We are punting on the decision to propose and discuss explicit network/VPN criteria.
Has anyone been assigned the task of proposing this new criterion?
I did it on Friday.
Found it in Buhzilla: "Using the default network configuration tools for the console and for release-blocking desktops, it must be possible to establish a working connection to common OpenVPN, openconnect-supported and vpnc-supported VNC servers with typical configurations.
Footnote title "Supported servers and configurations": As there are many different VPN server applications and configurations, blocker reviewers must use their best judgment in determining whether violations of this criterion are likely to be encountered commonly enough to block a release, and if so, at which milestone. As a general principle, the more people are likely to use affected servers and the less complicated the configuration required to hit the bug, the more likely it is to be a blocker."
Based on the above criteria, I tend to support this to be a blocker, because as the criteria says, a non-working VPN could prevent Fedora from being used and although I do not have any vpnconnect based VPN connection, I think the voice of people who have should be heard.
BetaBlocker +1
Found it in Buhzilla:
I'm not sure what bugzilla you're talking about, but the criterion has been proposed on the test list: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/ZK6FRRRWQNC3FQVX7ZTMUHQMPPEAZSJA/
It hasn't been approved yet, so we shouldn't vote yet. Or we should specifically say we expect this to be approved and base our vote on that assumption (to be revoked if it didn't turn out to be the case).
The Bugzilla discussion related to this bug.
I specifically think that this is going to be approved and therefore I have already cast my vote.
Discussed during a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2020-08-31/
AGREED AcceptedBetaBlocker This is accepted as a violation of the currently-under-discussion new networking criteria, as there has been no opposition to the idea that typical configs of common VPNs, including OpenConnect-supported VPNs, should work, and this is such a case
REVOTE BetaBlocker
there's been a lot of refinement and discussion in the Bugzilla bug and it seems that there's a clear question over whether this still needs to be a blocker, so I reset it to proposed blocker and am re-opening the voting here. Please vote again after reading the bug discussion. Thanks!
BetaBlocker -1
The scope seems to have narrowed enough that I'm okay with shipping this in Beta. I might consider it for a FinalBlocker once we have a better sense of the exact failure conditions.
Yeah, it's not even clear at this point if there is a bug.
The "should this still be a beta blocker?" part seems to be from https://bugzilla.redhat.com/show_bug.cgi?id=1863041#c58 onward. Still, I'm going to abstain from the vote, because I don't understand the topic very well.
BetaBlocker 0
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.