#fedora-qa: f18final-blocker-review-1.1
Meeting started by tflink at 17:01:41 UTC
(full logs).
Meeting summary
- Roll Call (tflink, 17:01:42)
- Introduction (tflink, 17:11:47)
- 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. (tflink,
17:12:04)
- We'll be following the process outlined
at: (tflink,
17:12:10)
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(tflink,
17:12:10)
- The bugs up for review today are available
at: (tflink,
17:12:17)
- http://qa.fedoraproject.org/blockerbugs/current
(tflink,
17:12:17)
- The criteria for release blocking bugs can be
found at: (tflink,
17:12:24)
- https://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria
(tflink,
17:12:25)
- https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria
(tflink,
17:12:25)
- https://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria
(tflink,
17:12:25)
- Up for review today are: (tflink,
17:12:34)
- 52 Proposed Blockers (tflink,
17:12:42)
- 3 Accepted Blockers (tflink,
17:12:42)
- 23 Proposed NTH (tflink,
17:12:42)
- 1 Accepted NTH (tflink,
17:12:42)
- The meeting will be capped at 3 hours. If we
are not done by then, another meeting will be scheduled.
(tflink,
17:14:52)
- (876716) anaconda crashes after setting root password (tflink, 17:17:04)
- https://bugzilla.redhat.com/show_bug.cgi?id=876716
(tflink,
17:17:04)
- Proposed Blocker, anaconda, NEW (tflink,
17:17:04)
- AGREED: 876716 - It
seems as if more people are hitting this than show up on the bug but
we still don't have a reliable reproducing case or debug info - will
wait on decision in case either one of those things is found and
revisit later. (tflink,
17:23:27)
- (869424) RuntimeError: Error running systemctl: No such file or directory (tflink, 17:23:36)
- https://bugzilla.redhat.com/show_bug.cgi?id=869424
(tflink,
17:23:39)
- Proposed Blocker, anaconda, ASSIGNED
(tflink,
17:23:41)
- AGREED: 869424 - This
needs to be re-tested with latest anaconda in order to determine
whether or not the original bug has been fixed. Will re-visit after
the re-testing is complete (tflink,
17:34:11)
- (880263) DMError: partition activation failed for 'mpatha' (tflink, 17:34:28)
- https://bugzilla.redhat.com/show_bug.cgi?id=880263
(tflink,
17:34:28)
- Proposed Blocker, anaconda, NEW (tflink,
17:34:28)
- AGREED: 880263 -
AcceptedBlocker - Violates the following F18 alpha release criterion
for systems using LVM on mpath: "The installer must boot and run on
all primary architectures, with all system firmware types that are
common on those architectures, from default live image, DVD, and
boot.iso install media ..." (tflink,
17:58:07)
- (876218) kernel boot + nfsiso repo = hang on reboot (tflink, 17:58:18)
- https://bugzilla.redhat.com/show_bug.cgi?id=876218
(tflink,
17:58:18)
- Proposed Blocker, anaconda, ASSIGNED
(tflink,
17:58:18)
- AGREED: 876218 -
AcceptedBlocker - Violates the following F18 release criterion for
reboots during/after NFSISO based installs: "Any installation method
or process designed to run unattended must do so (there should be no
prompts requiring user intervention)" (tflink,
18:20:43)
- (875599) anaconda keeping error status after Change the installation source to point to a custom HTTP/FTP repository (tflink, 18:20:49)
- https://bugzilla.redhat.com/show_bug.cgi?id=875599
(tflink,
18:20:52)
- Proposed Blocker, anaconda, NEW (tflink,
18:20:55)
- AGREED: 875599 -
RejectedBlocker, AcceptedNTH - While this is a problem with a rather
non-intuitive solution, it doesn't clearly violate any of the F18
release criteria. A well-tested fix would be considered after
freeze. (tflink,
18:32:08)
- (858628) Some buttons and labels in Anaconda can't be localized (tflink, 18:32:24)
- https://bugzilla.redhat.com/show_bug.cgi?id=858628
(tflink,
18:32:25)
- Proposed Blocker, anaconda, NEW (tflink,
18:32:25)
- AGREED: 858628 -
AcceptedBlocker - Prevents translation of some strings in the
installer and thus violates the following F18 final release
criterion: "All critical path actions on release-blocking desktop
environments should correctly display all sufficiently complete
translations available for use" (tflink,
18:37:01)
- (875477) ValueError: name already in use (tflink, 18:37:14)
- https://bugzilla.redhat.com/show_bug.cgi?id=875477
(tflink,
18:37:14)
- Proposed Blocker, anaconda, ASSIGNED
(tflink,
18:37:14)
- AGREED: 875477 -
AcceptedBlocker - Violates the following F18 beta release criterion:
"The installer's custom partitioning mode must be capable of the
following: Creating, destroying and assigning mount points to
partitions of any specified size using most commonly-used filesystem
types ..." (tflink,
18:44:30)
- (876547) ValueError: ('invalid size specification', '-472.028417969 mb') (tflink, 18:44:48)
- https://bugzilla.redhat.com/show_bug.cgi?id=876547
(tflink,
18:44:51)
- Proposed Blocker, anaconda, NEW (tflink,
18:44:54)
- AGREED: 876547 - At
this point, there aren't enough debug logs or reproducers to make a
call on blocker status, will revisit when there is more available
information and more tests done. (tflink,
18:58:25)
- (873293) custom storage ui fails to create lvm unless all disks have free space (tflink, 18:58:37)
- https://bugzilla.redhat.com/show_bug.cgi?id=873293
(tflink,
18:58:40)
- Proposed Blocker, anaconda, ASSIGNED
(tflink,
18:58:42)
- AGREED: 873293 -
RejectedBlocker, AceptedNTH - This isn't a crash but it would be
nice if the installer had a clearer error message to identify the
cause of this issue, it is recoverable. Rejected as a blocker for
F18 final but a tested fix would be considered past freeze.
(tflink,
19:14:05)
- (876789) FormatDestroyError: error wiping old signatures from /dev/md/Volume0_0p2: 1 (tflink, 19:14:29)
- https://bugzilla.redhat.com/show_bug.cgi?id=876789
(tflink,
19:14:32)
- Proposed Blocker, anaconda, NEW (tflink,
19:14:34)
- AGREED: 876789 -
AcceptedBlocker - Violates the following F18 beta release criterion
for existing LVM LVs: "The installer's custom partitioning mode must
be capable of the following: Creating, destroying and assigning
mount points to partitions of any specified size using most
commonly-used filesystem types ..." (tflink,
19:19:30)
- (879612) OSError: [Errno 2] No such file or directory: '/mnt/install/isodir/dvd.iso' (tflink, 19:19:46)
- https://bugzilla.redhat.com/show_bug.cgi?id=879612
(tflink,
19:19:49)
- Proposed Blocker, anaconda, NEW (tflink,
19:19:51)
- AGREED: 879612 -
AcceptedBlocker - Violates the following F18 final release criteria
for using a local iso as an installation source: "The installer must
be able to use all supported local and remote package source
options" (tflink,
19:27:03)
- (879610) SystemError: (32, 'umount: /run/install/isodir: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))') (tflink, 19:27:42)
- https://bugzilla.redhat.com/show_bug.cgi?id=879610
(tflink,
19:27:45)
- Proposed Blocker, anaconda, NEW (tflink,
19:27:48)
- AGREED: 879610 -
AcceptedBlocker - Violates the following F18 final release criteria
for using a local iso as an installation source: "The installer must
be able to use all supported local and remote package source
options" (tflink,
19:31:37)
- (869978) %packages --default doesn't install default system, but minimal one (tflink, 19:32:00)
- https://bugzilla.redhat.com/show_bug.cgi?id=869978
(tflink,
19:32:03)
- Proposed Blocker, anaconda, ASSIGNED
(tflink,
19:32:06)
- ACTION: kparal to
start thread on test@ about a possible new kickstart release
criterion (tflink,
19:47:28)
- AGREED: 869978 -
While this doesn't hit any of the current F18 release criteria,
there is discussion about adding a new release criterion to cover a
subset of kickstart options. Will re-visit after discussion on
test@ (tflink,
19:50:05)
- (864087) wired ethernet defaults to Off in certain situations (tflink, 19:50:15)
- https://bugzilla.redhat.com/show_bug.cgi?id=864087
(tflink,
19:50:15)
- Proposed Blocker, anaconda, NEW (tflink,
19:50:15)
- AGREED: 864087 -
RejectedBlocker, AcceptedNTH - While this can be nonintuitive to
discover and figure out post-install, it doesn't directly violate
any F18 release criterion and could be fixed post-install. If it
turns out that this affects lives pre-install, please re-propose as
a blocker (tflink,
19:57:13)
- Hit the 3 hour mark, stopping the review
meeting (tflink,
19:57:40)
- Next Review Meeting (tflink, 19:57:55)
- we covered 14/52 proposed blockers and 0/23
proposed NTH in today's review meeting (tflink,
20:03:41)
- it's unclear what time is best for a continued
review, will discuss with possibly interested parties and send
announcement (tflink,
20:04:19)
- ACTION: tflink to
find people and time for the blocker review meeting
continuation (tflink,
20:04:45)
- Open Floor (tflink, 20:05:29)
Meeting ended at 20:07:04 UTC
(full logs).
Action items
- kparal to start thread on test@ about a possible new kickstart release criterion
- tflink to find people and time for the blocker review meeting continuation
Action items, by person
- kparal
- kparal to start thread on test@ about a possible new kickstart release criterion
- tflink
- tflink to find people and time for the blocker review meeting continuation
People present (lines said)
- tflink (256)
- kparal (178)
- adamw (148)
- dlehman (26)
- akshayvyas (26)
- pschindl (24)
- zodbot (12)
- wwoods (7)
- cpuobsessed (5)
- cpu (2)
- drindt (1)
- satellit (1)
- Viking-Ice (1)
- Southern_Gentlem (1)
Generated by MeetBot 0.1.4.