Hi folks! Here is your start-of-the-week blocker bug status report. We currently have the following open accepted blockers which need to be resolved for RC2: * https://bugzilla.redhat.com/show_bug.cgi?id=1156354 - "ValueError: cannot modify protected device" * https://bugzilla.redhat.com/show_bug.cgi?id=1156614 - "mdraid set name different between anaconda and installed system - causes failure of installed system to boot" These are both firmware RAID handling issues for which dlehman has submitted patches for review; we need the patches to be reviewed and a new anaconda build done which incorporates the patches. * https://bugzilla.redhat.com/show_bug.cgi?id=1156603 - "Cloud images aren't being generated at compose time" This has been known for a while but we only just started tracking it with a blocker bug. At present release engineering are still working to figure out just why the cloud image generation seems to keep failing. It's not yet clear whether any changes to the package set will be required to fix it, or only to the generation process. We have one proposed blocker outstanding, for which we could really use input from the device-mapper-multipath maintainers: * https://bugzilla.redhat.com/show_bug.cgi?id=1154347 - "Anaconda fails to recognize local standard SATA disks after secure-erase" It seems multipathd erroneously recognizes regular disks as multipath devices sometimes, which can result in them not being available as installation targets in anaconda. This is worrisome, but we really need some input from the maintainers to have any idea whether it's likely to be common enough to qualify as a blocker bug. We have (I think) just one update that requires karma at present: https://admin.fedoraproject.org/updates/uboot-tools-2014.10-1.fc21 that can be up-karmaed by anyone who has successfully tested a Fedora 21 Beta RC1 ARM image, as it was used to compose those images. I'd like to be able to request the RC2 compose ideally today but at the latest by tomorrow, so at a minimum we really need the anaconda build with the RAID fixes ASAP. It will be reasonable to submit the RC2 compose request at that point, as it's possible the Cloud generation issues can be resolved during RC2 compose and that #1154347 is ultimately decided not to be be a blocker. Thanks for all your help and work, everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
