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:20)
We'll be following the process outlined
at:(adamw,
16:06:20)
AGREED: 1477916 -
punt (delay decision) - we did not yet get around to testing this in
more detail or drafting a revised criterion, so we will punt (delay)
this one again and try to get it done this week(adamw,
16:31:58)
(1455561) ipa-server-install fails to obtain RA certificate from CA (CA_UNREACHABLE)(adamw, 16:32:38)
AGREED: 1455561 -
AcceptedBlocker (Beta) - clear violation of "Release-blocking roles
and the supported role configuration interfaces must meet the core
functional Role Definition Requirements to the extent that supported
roles can be successfully deployed..." for the release-blocking
'domain controller' role(adamw,
16:39:20)
(1487305) Raspberry Pi 3: run-initial-setup hangs(adamw, 16:40:44)
AGREED: 1487305 -
AcceptedBlocker (Beta) - this sounds like a violation of Alpha
criterion "A working mechanism to create a user account must be
clearly presented during installation and/or first boot of the
installed system" for Raspberry Pi 3, which is a supported ARM
platform for F27. If further testing indicates it's not so
clear-cut, we will revisit(adamw,
16:53:16)
(1484155) rdma-core excluding armhfp breaks many, many dep chains(adamw, 16:53:27)
this is pretty much solved now, at least to the
point where it isn't blocking composes or obviously breaking
critical functionality any more(adamw,
16:54:13)
we will un-propose or close the bug(adamw,
16:54:21)
(1484566) Multiple 'map' denials prevent Cockpit from working(adamw, 16:55:32)
AGREED: 1484566 -
AcceptedBlocker (Beta) - clear violation of Alpha criterion "Unless
explicitly specified otherwise, after system installation the
Cockpit web management interface must be running and accessible on
its default port (9090)"(adamw,
17:00:57)
AGREED: 1486002 -
AcceptedBlocker (Beta) - we're happy to accept Konrad's assertion
that this violates the Final criterion "The release must boot
successfully as Xen DomU with releases providing a functional,
supported Xen Dom0 and widely used cloud providers utilizing
Xen"(adamw,
17:15:58)
(1484575) Filesystem resizing during install fails since 2.1.10 (likely due to removal of unconditional filesystem check)(adamw, 17:16:08)
AGREED: 1486002 -
AcceptedBlocker (Final) - clear violation of Final criterion "Any
installer mechanism for resizing storage volumes must correctly
attempt the requested operation"(adamw,
17:24:26)
(1484908) xenconsole does want to start(adamw, 17:24:39)
AGREED: 1484908 -
punt (delay decision) - it's not clear whether this actually
violates the criterion, so we will request a more detailed
explanation from Konrad(adamw,
17:34:30)