Our purpose in this meeting is to review
proposed blocker and nice-to-have bugs and decide whether to accept
them, and to monitor the progress of fixing existing accepted
blocker and nice-to-have bugs.(adamw,
16:06:05)
We'll be following the process outlined
at:(adamw,
16:06:05)
AGREED: 1503496 -
AcceptedBlocker (Final) - violates "The installer must be able to
install into free space alongside an existing OS X installation,
install and configure a bootloader that will boot Fedora" (and all
'must complete installation' criteria for Macs)(adamw,
16:19:59)
(1489942) dbxtool fails at boot 'Could not apply database update "DBXUpdate-2016-08-09-13-16-00.bin": Permission denied'(adamw, 16:20:10)
AGREED: 1489942 -
RejectedBlocker AcceptedFreezeException (Final) - this is rejected
as a blocker on the basis it won't affect all installs (we believe
it affects UEFI non-Secure Boot installs) and there is no real
practical consequence of the error. However, fixing this will
improve release polish and that can't be done with an update, so
accepted FE.(adamw,
16:37:03)
(1504059) Include Firefox 57 at compose(adamw, 16:37:12)
AGREED: 1504059 -
punt (delay decision) - FESCo's intent is not clear to us, given the
wording of their agreement and the lack of context in the meeting
logs. we ask FESCo to clarify their intent on what should be done
with FF57 in F27, given that it is *not* in stable but
updates-testing and the maintainer would like to push it stable.
does FESCo mean for this to be blocker, or FE, and what ff57
build(s) is it expecting when?(adamw,
16:54:24)
AGREED: 1497691 -
AcceptedBlocker (Final) - clearly violates "The release must contain
no known security bugs of 'important' or higher impact according to
the Red Hat severity classification scale which cannot be
satisfactorily resolved by a package update (e.g. issues during
installation)"(adamw,
16:58:43)
(1500834) VirtualBox: black screen on fedora 27(adamw, 16:58:53)
AGREED: 1500834 -
RejectedBlocker (Final) AcceptedFreezeException (Final) - vbox isn't
one of the officially-blocking virt technologies and a workaround is
available so we don't think this qualifies as a blocker, but as vbox
is widely used we certainly think it's worth a freeze
exception(adamw,
17:06:08)
(1501762) CVE-2017-5123 kernel: Missing access_ok() checks in waitid() [fedora-all](adamw, 17:06:15)
AGREED: 1501762 -
AcceptedBlocker (Final) - violates "The release must contain no
known security bugs of 'important' or higher impact according to the
Red Hat severity classification scale which cannot be satisfactorily
resolved by a package update (e.g. issues during
installation)."(adamw,
17:10:27)
(1502915) World map missing in Time & Date(adamw, 17:10:35)
AGREED: 1502915 -
RejectedBlocker (Final) AcceptedFreezeException (Final) - this does
not seem to violate any existing criterion, but is a very obvious
error in the installer so we're happy to grant it a freeze
exception.(adamw,
17:15:52)
(1501362) Intel microcode not updating --> [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)(adamw, 17:16:00)
AGREED: 1501362 -
RejectedBlocker (Final) RejectedFreezeException (Final) - as we
understand this, nothing is really broken, it's just a warning about
a feature that could be enabled with a microcode update. we think a
regular update is the best way to fix this, rushing a fix in via
blocker/FE is not needed and potentially dangerous.(adamw,
17:22:54)
continuing with proposed Server Beta
blockers(adamw,
17:23:22)
AGREED: 1503321 -
AcceptedBlocker (Server Beta) - adam's not entirely sure if the
upgrade criterion technically covers this, but there's strong
agreement that we do *intend* to require that release-blocking
server roles upgrade successfully, so this is accepted and adam will
propose a criteria change to make the intent clearer(adamw,
17:53:44)
(1504602) Image build fails because of dracut warning "/dev/root does not exist"(adamw, 17:53:51)
AGREED: - 1504602 -
AcceptedBlocker (Server Beta) - we believe this failure dooms the
compose even though the task only fails on two non-blocking arches,
thus this is accepted as it prevents compose working at all(adamw,
18:05:57)
(1504745) Modular server autopart gives invalid partitioning(adamw, 18:06:06)
(1478141) Anaconda gives a traceback if there is non-activated InfiniBand network device present during an attempt to install in text mode(adamw, 18:15:52)
AGREED: 1478141 -
AcceptedFreezeException (Final) - this obviously can't be fixed by
an update and will inconvenience anyone who runs into it, fixing it
is definitely worth a freeze exception(adamw,
18:24:27)
(1487787) corosync libraries built with work-in-progress fix in libqb so as to re-establishing compatibility with ld from binutils 2.29 unusuable on powerpc platforms for further link(adamw, 18:24:36)
AGREED: 1487787 -
AcceptedFreezeException (Final) - this seems to affect build and
correct functionality of several packages and dependency chains on a
couple of non-release blocking arches, it would be good to
straighten that out in stable rather than waiting for a post-release
update(adamw,
18:31:51)
(1499260) Failing HTM tbegin for z Series guests despite claiming support.(adamw, 18:32:03)
AGREED: 1499260 -
AcceptedFreezeException (Final) - this breaks installer boot on a
non-blocking arch (s390x), so obviously cannot be fully fixed with
an update and is serious enough to grant an FE(adamw,
18:37:29)
(1502827) gnome-initial-setup 'user creation' mode no longer runs after install with no user account (since 3.26.1)(adamw, 18:37:44)
AGREED: 1502827 -
AcceptedFreezeException (Final) - this is a prominent incorrect
behaviour in the initial install and boot workflow, cannot be fully
fixed with an update(adamw,
18:47:40)
(1478089) logging feature silently severed due to changed treatment of orphaned sections in ld.bfd/binutils-2.29(adamw, 18:47:51)
AGREED: 1500734 -
AcceptedBlocker (Final) - violates "The release must contain no
known security bugs of 'important' or higher impact according to the
Red Hat severity classification scale which cannot be satisfactorily
resolved by a package update (e.g. issues during installation)", as
this is rated 'important' and SDL may be used during live
sessions(adamw,
18:59:29)