Hi, folks! Time (and past time) for a Fedora 22 blocker status review. Sorry this is late; we've been fighting fires for the last week :( Here are your outstanding blockers requiring attention from test, devel, or both: ARM/KERNEL: https://bugzilla.redhat.com/show_bug.cgi?id=1183807 "network spoke listed as not connected despite having assigned IP and hostname" - anaconda team have the impression that this is an ARM- specific kernel issue to do with renaming of ethernet devices on ARM; could do with input from ARM folks. ANACONDA: https://bugzilla.redhat.com/show_bug.cgi?id=1197290 "realm crash during kickstart" - this needs re-testing with the fixed anaconda, except the 'fixed' anaconda is DOA due to other issues; I've alerted the anaconda team to the issues. CLOUD: https://bugzilla.redhat.com/show_bug.cgi?id=1194490 "Recent cloud builds fail to boot with kernel panic" - this could do with a status update; I get the impression it may be a bit out of date, but as of now it shows as NEW. Could cloud folks please review? FREEIPA / SSSD: https://bugzilla.redhat.com/show_bug.cgi?id=1197218 "Add missing dependencies into freeipa packages" - this still appears to need attention, but it may no longer block release as https://bugzilla.redhat.com/show_bug.cgi?id=1014594 has been pulled in as a freeze exception. It would be good to get clarification on the current status - sgallagh? FREEIPA: https://bugzilla.redhat.com/show_bug.cgi?id=1195811 "PKI fails to install, missing support for Tomcat 8.0" - the Tomcat 7 revert is built and in updates-testing thanks to sgallagh, we will need to test it now, whether with scratch images or by rolling a TC9 tomorrow. NETWORKMANAGER: https://bugzilla.redhat.com/show_bug.cgi?id=1193127 "dhclient is started by NetworkManager at disconnection instead of at connection time" - this seems to be a straight-up NM bug affecting wired network connections on some hardware (at least recent Thinkpads) that still requires developer attention. XORG: https://bugzilla.redhat.com/show_bug.cgi?id=1196676 "X fails to start when booting x86_64 netinst on basic graphic mode (nomodeset)" - this requires developer attention; it's been discussed on the list already, but a fix hasn't appeared yet. For testers, the list of builds requiring karma is quite light right now. As anaconda is currently known to be broken, it's really only the tomcat reversion, https://admin.fedoraproject.org/updates/tomcat-7.0.59-3.fc22 . It would help a lot if folks who are able to test FreeIPA deployments can test with that Tomcat and confirm that FreeIPA works with it. We will probably want to roll a new compose tomorrow, ideally with an updated anaconda, but we cannot roll an RC yet due to several blockers still being outstanding (most of the above). As Go/No-Go is scheduled for Thursday we're unfortunately very likely to slip Alpha at this point :( Despite our attempts to test earlier in the cycle, many late-landing changes caused problems, and we were not able to test the flavor/Product-ized images until the first TC landed. The GCC rebuild certainly seems to have caused its fair share of havoc :(. Aside from the bugs listed above we have a near-blocker for the KDE images - https://bugzilla.redhat.com/show_bug.cgi?id=1194682 - which is still being worked on. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
