As per the Fedora 22 schedule [1], Fedora 22 Beta Test Compose 6 (TC6) is now available for testing.
Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/6132#comment:10 . Please see the following pages for download links and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download- ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace "dl" with "download-ib01" in the download URL.
Installation:
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
Base:
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
Workstation and Desktop:
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
Server:
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
Cloud:
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
Summary:
https://fedoraproject.org/wiki/Test_Results:Current_Summary
All Beta priority test cases for each of these test pages [2] must pass in order to meet the Beta Release Criteria [3]. For the Fedora 22 cycle we are also trying to run the Final tests at this time, to try and identify later release blocker bugs as early as possible.
Help is available on #fedora-qa on irc.freenode.net [4], or on the test list [5].
Create Fedora 22 Beta test compose (TC) and release candidate (RC) https://fedorahosted.org/rel-eng/ticket/6132
Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current
[1] http://fedorapeople.org/groups/schedule/f-22/f-22-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria [4] irc://irc.freenode.net/fedora-qa [5] https://admin.fedoraproject.org/mailman/listinfo/test
On 03/31/2015 08:26 AM, Adam Williamson wrote:
As per the Fedora 22 schedule [1], Fedora 22 Beta Test Compose 6 (TC6) is now available for testing.
I'm trying a Server kickstart install on a VM with updates-testing enabled. It hangs near/at the end of package installing. top reports a crazy high load average (106) and machine basically locks up. systemd appears to be in D state. Last journalctl message is:
unknown: <audit-1327> proctitle="load_policy"
On Tue, 2015-03-31 at 14:20 -0600, Orion Poplawski wrote:
On 03/31/2015 08:26 AM, Adam Williamson wrote:
As per the Fedora 22 schedule [1], Fedora 22 Beta Test Compose 6 (TC6) is now available for testing.
I'm trying a Server kickstart install on a VM with updates-testing enabled. It hangs near/at the end of package installing. top reports a crazy high load average (106) and machine basically locks up. systemd appears to be in D state. Last journalctl message is:
unknown: <audit-1327> proctitle="load_policy"
Does it happen without u-t? What's the kickstart? Thanks!
On 03/31/2015 02:54 PM, Adam Williamson wrote:
On Tue, 2015-03-31 at 14:20 -0600, Orion Poplawski wrote:
On 03/31/2015 08:26 AM, Adam Williamson wrote:
As per the Fedora 22 schedule [1], Fedora 22 Beta Test Compose 6 (TC6) is now available for testing.
I'm trying a Server kickstart install on a VM with updates-testing enabled. It hangs near/at the end of package installing. top reports a crazy high load average (106) and machine basically locks up. systemd appears to be in D state. Last journalctl message is:
unknown: <audit-1327> proctitle="load_policy"
Does it happen without u-t? What's the kickstart? Thanks!
It happens without u-t. More debugging seems to show a hang trying to access the systemd process image:
http://sw.cora.nwra.com/tmp/Screenshot_vmf22_hang.png
But unclear if that is cause, or just symptom.
Next attempt to get more info resulted in a successful install, so yay, some kind of race. It appears to be hanging in the post rpm transaction scriptlet stuff and probably in the glibc.i686 %post scriptlet, which is /usr/sbin/glibc_post_upgrade.i686 - and yay, a binary.
Seems to be here:
if (check_elf ("/proc/1/exe")) verbose_exec (116, "/sbin/telinit", "/sbin/telinit", "u");
in check_elf()
But again, all IO seems to be stuck at this point, so could be symptom, not a trigger.
Install is a x86_64 system, but I install some 32bit libraries as well.