Test Day:2010-09-07 Systemd

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Test Results)
(Test Results)
(36 intermediate revisions by 14 users not shown)
Line 21: Line 21:
 
== What's needed to test ==  
 
== What's needed to test ==  
  
* An updated [http://fedoraproject.org/get-prerelease {{FedoraVersion|long|next}} pre-release], or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/ nightly live image]
+
* An updated [http://fedoraproject.org/get-prerelease {{FedoraVersion|long|next}} pre-release], or the special live image (see [[Test Day:2010-09-07_Systemd#Live_image|below]])
 +
* Not-yet-published updates for ''systemd'', ''initscripts'', ''dbus'', ''ConsoleKit'' and ''acpid'' (see below for details)
  
 
== How to test? ==
 
== How to test? ==
Line 30: Line 31:
  
 
=== '''Live image''' ===
 
=== '''Live image''' ===
 +
=== '''Live image''' ===
 +
 +
Optionally, you may download a non-destructive {{FedoraVersion|long|next}} live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
 +
 +
{|
 +
! Architecture !! SHA256SUM
 +
|-
 +
| [http://adamwill.fedorapeople.org/systemd_test_day_20100907/systemd_20100907_i686.iso i686] || FIXME
 +
|-
 +
| [http://adamwill.fedorapeople.org/systemd_test_day_20100907/systemd_20100907.iso x86_64] || 216ce365ae67af28832c85fe0a352f58967f90d4dad02abaf9b666714ffd522a
 +
|-
 +
|}
 +
 +
This custom live image contains all the necessary updated packages. You will not be able to conduct the full range of tests using the live CD, but you can perform the tests that are possible, and confirm that it boots correctly on your system. You can also use it to install a Fedora 14 system to perform the full range of tests.
 +
 +
=== Install additional updates ===
 +
 +
To provide the best test results, please install the following packages. They have not yet been accepted as official Fedora 14 updates, but they fix several known issues with systemd. If you test with or install from the custom live image linked to above, these updates will already be installed.
  
Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
+
From koji:
 +
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=193591 systemd-9-3.fc14]
 +
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=194171 initscripts-9.19-1.fc14]
 +
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=193903 dbus-1.4.0-1.fc14]
 +
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=193894 ConsoleKit-0.4.2-1.fc14]
 +
* acpid-2.0.5-2.1.fc14 - [http://adamwill.fedorapeople.org/systemd_test_day_20100907/acpid-2.0.5-2.1.fc14.i686.rpm i686], [http://adamwill.fedorapeople.org/systemd_test_day_20100907/acpid-2.0.5-2.1.fc14.x86_64.rpm x86_64]
  
 
=== Test ===
 
=== Test ===
Line 60: Line 84:
 
| <references/>
 
| <references/>
 
|-
 
|-
|}
+
| [[royboy626|Ron Humble]]
 +
| {{result|pass}} <ref>Test pass, All Ker Param boots OK. Not yet verify Results 3,4,5,6. Hope to do more.</ref>
 +
| {{result|fail}} <ref>N/A</ref>
 +
| <references/>
 +
|-
 +
| [[zbyszek|Zbyszek Jędrzejewski-Szmek]]
 +
| {{result|warn}} <ref>Output is messy: "Halting...Stopping auditd[ OK ]stemctl):", but the next lines are OK</ref> <ref>Asking for runlevel 1, single, s, S or -s booted into runlevel "unknown" (as reported by {{command|runlevel}}) {{bz|630914}}</ref>
 +
| {{result|warn}} <ref>AD 3: Asking for runlevel 4 or 2 runlevel runlevel is reported as 3</ref> <ref>AD 3: After {{command|init 1}} the old runlevel is still reported (3 or 5)</ref> <ref>AD 12: {{command|service netconsole start}} prints 'Starting netconsole (via systemctl): [OK]', but {{command|systemctl status netconsole}} shows '...exited, status 6/NOTCONFIGURED' and netconsole is really not loaded</ref> <ref>AD 19: corrected a bug in Expected Results</ref>
 +
| <references/><br>The rest passes without problem!
  
 +
|-
 +
| [[urban|Krzysztof Urbaniak]]
 +
| {{result|pass}} <ref>Booting to different runlevels works, (s|S|single) works, changing the default runlevel works.</ref>
 +
| {{result|warn}} <ref>Works almost all, i'll have small issues with telinit 1,2,3,4,5, but its not critical.</ref>
 +
| <references/>
 +
|-
 +
| [[User:tedroche|Ted Roche]]
 +
| {{result|warn}} <ref>LiveUSB-32, Forcing runlevel 3 reported runlevel "unknown" (as reported by 'runlevel' command) {{bz|630914}} but later (after 'ps' and 'top' and 'telinit 5') reports runlevel 3 5. Shutdown, reboot and teleinit as expected. </ref>
 +
| {{result|pass}}<ref>Reboot, shutdown and telinit working; not all variants exercised due to time constraints.</ref>
 +
| <references/>
 +
 +
|-
 +
| [[ac000|Andrew Clayton]]
 +
| {{result|pass}}
 +
| {{result|warn}} <ref>telinit has problems as in {{bz|627014}}</ref> <ref> shutdown -k doesn;t work as it should. {{bz|624149#c20}}</ref>
 +
| <references/>
 +
 +
|-
 +
| [[User:Renault|Charles-Antoine Couret]]
 +
| {{result|warn}} <ref>KDE not shutdown in {{bz|631588}}</ref> <ref>The single mode is not correct, I have a different prompt, in {{bz|631590}}</ref>
 +
| {{result|pass}}
 +
| <references/>
 +
|-
 +
| [[User:Thub|Thub]]
 +
| {{result|warn}} <ref>Runlevel 1 does not update the runlevel reported by "runlevel" command, either at boot or via telinit (reported above). {{bz|630914}}</ref>
 +
<ref>Booting to runlevel 3 when firstboot hasn't been run yet results in firstboot and getty trying to use the same tty. {{bz|631584}}</ref>
 +
| {{result|fail}} <ref>telinit fails to change runlevels properly (e.g. telinit 5 does not start X unless the system booted to runlevel 5 initially). {{bz|627014}}</ref>
 +
<ref>"halt" command: No indication that it has halted. {{bz|631592}}</ref>
 +
<ref>"halt -p", "poweroff", and "shutdown -h" commands and their rebooting equivalents, when invoked in runlevel 5, appear to cause gdm to be restarted, rather than stopped. {{bz|631160}}</ref>
 +
| <references/>
 +
|-
 +
| [[User:jcm|Jon Masters]]
 +
| {{result|warn}} When booted with "console=tty console=ttyS0" or "console=ttyS0", there is no getty on tty1.
 +
| {{result|fail}} "halt" used to also shut down the system, does not do so any longer (I know this has been discussed, I'm specifically calling it out). Additionally, on current <b>rawhide</b>: (systemd-9-3.fc15.x86_64) the root filesystem always has busy inodes on shutdown and forces a replay of the journal on next boot, lvm2-monitor does not shutdown cleanly on halt, various log entries contain "init[1]: Got invalid poll event on pipe." followed by e.g. "init[1]: Unit sys-kernel-security.automount entered failed state.", and there are several "mount" errors when systemd re-execs itself to apparently try to handle the busy inodes situation.
 +
| Some testing on F-14, some on rawhide. Seems to work ok, but there are some behavioral changes.
 +
|-
 +
| [[User:Dramsey|David Ramsey ]]
 +
| {{result|warn}} <ref>{{bz|630914}}</ref> <ref>Was RHBZ #[https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=630915 630915] now listed as {{bz|630935}}</ref>
 +
| {{result|warn}} <ref>{{bz|631592}}</ref> <ref>{{bz|631160}}</ref>
 +
| <references/><br>system's [http://www.smolts.org/client/show/pub_153a5c6a-3441-43b6-971f-41f92dc83842 smolt data]
 +
|-
 +
| [[User:Rhe|He Rui]]
 +
| {{result|warn|rhe|630914|630915}}
 +
| {{result|none}}
 +
| <references/>
 +
|-
 +
|}
 
[[Category:Fedora 14 Test Days]]
 
[[Category:Fedora 14 Test Days]]

Revision as of 08:46, 29 September 2010

DATE TIME WHERE
Tue Sept 07, 2010 All day #fedora-test-day (webirc)
Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule - which should be linked at QA/Test_Days - and see if a similar but more recent Test Day is planned or has already happened.

Contents

What to test?

Today's installment of Fedora Test Day will focus on systemd, the new initialization system being introduced in Fedora 14.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion...

What's needed to test

  • An updated Fedora 21 pre-release, or the special live image (see below)
  • Not-yet-published updates for systemd, initscripts, dbus, ConsoleKit and acpid (see below for details)

How to test?

Update your machine

If you're running Fedora 14, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live image

Live image

Optionally, you may download a non-destructive Fedora 21 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture SHA256SUM
i686 FIXME
x86_64 216ce365ae67af28832c85fe0a352f58967f90d4dad02abaf9b666714ffd522a

This custom live image contains all the necessary updated packages. You will not be able to conduct the full range of tests using the live CD, but you can perform the tests that are possible, and confirm that it boots correctly on your system. You can also use it to install a Fedora 14 system to perform the full range of tests.

Install additional updates

To provide the best test results, please install the following packages. They have not yet been accepted as official Fedora 14 updates, but they fix several known issues with systemd. If you test with or install from the custom live image linked to above, these updates will already be installed.

From koji:

Test

Follow each of these test cases:

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component systemd. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.

User Basic Tools References
Sample User
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
Kamil Páral
Warning warn
[1] [2] [3] [4] [5]
none
  1. Asking for runlevel 4 or 2 booted into runlevel 3
  2. Asking for runlevel 1, single, s, S or -s booted into runlevel "unknown" (as reported by 'runlevel' command) RHBZ #630914
  3. ConsoleKit logs doesn't seem to include required information, but testcase documentation is too scarce.
  4. When booted with console=ttyS0 option, tty1 is not started.
  5. Error line on poweroff: Stopping rpcbind (via systemctl): /etc/init.d/killall: line 16: 1654 Terminated /etc/init.d/$subsys stop RHBZ #630915
Ron Humble
Pass pass
[1]
Fail fail
[2]
  1. Test pass, All Ker Param boots OK. Not yet verify Results 3,4,5,6. Hope to do more.
  2. N/A
Zbyszek Jędrzejewski-Szmek
Warning warn
[1] [2]
Warning warn
[3] [4] [5] [6]
  1. Output is messy: "Halting...Stopping auditd[ OK ]stemctl):", but the next lines are OK
  2. Asking for runlevel 1, single, s, S or -s booted into runlevel "unknown" (as reported by runlevel) RHBZ #630914
  3. AD 3: Asking for runlevel 4 or 2 runlevel runlevel is reported as 3
  4. AD 3: After init 1 the old runlevel is still reported (3 or 5)
  5. AD 12: service netconsole start prints 'Starting netconsole (via systemctl): [OK]', but systemctl status netconsole shows '...exited, status 6/NOTCONFIGURED' and netconsole is really not loaded
  6. AD 19: corrected a bug in Expected Results

The rest passes without problem!
Krzysztof Urbaniak
Pass pass
[1]
Warning warn
[2]
  1. Booting to different runlevels works, (s|S|single) works, changing the default runlevel works.
  2. Works almost all, i'll have small issues with telinit 1,2,3,4,5, but its not critical.
Ted Roche
Warning warn
[1]
Pass pass
[2]
  1. LiveUSB-32, Forcing runlevel 3 reported runlevel "unknown" (as reported by 'runlevel' command) RHBZ #630914 but later (after 'ps' and 'top' and 'telinit 5') reports runlevel 3 5. Shutdown, reboot and teleinit as expected.
  2. Reboot, shutdown and telinit working; not all variants exercised due to time constraints.
Andrew Clayton
Pass pass
Warning warn
[1] [2]
  1. telinit has problems as in RHBZ #627014
  2. shutdown -k doesn;t work as it should. RHBZ #624149#c20
Charles-Antoine Couret
Warning warn
[1] [2]
Pass pass
  1. KDE not shutdown in RHBZ #631588
  2. The single mode is not correct, I have a different prompt, in RHBZ #631590
Thub
Warning warn
[1]

[2]

Fail fail
[3]

[4] [5]

  1. Runlevel 1 does not update the runlevel reported by "runlevel" command, either at boot or via telinit (reported above). RHBZ #630914
  2. Booting to runlevel 3 when firstboot hasn't been run yet results in firstboot and getty trying to use the same tty. RHBZ #631584
  3. telinit fails to change runlevels properly (e.g. telinit 5 does not start X unless the system booted to runlevel 5 initially). RHBZ #627014
  4. "halt" command: No indication that it has halted. RHBZ #631592
  5. "halt -p", "poweroff", and "shutdown -h" commands and their rebooting equivalents, when invoked in runlevel 5, appear to cause gdm to be restarted, rather than stopped. RHBZ #631160
Jon Masters
Warning warn
When booted with "console=tty console=ttyS0" or "console=ttyS0", there is no getty on tty1.
Fail fail
"halt" used to also shut down the system, does not do so any longer (I know this has been discussed, I'm specifically calling it out). Additionally, on current rawhide: (systemd-9-3.fc15.x86_64) the root filesystem always has busy inodes on shutdown and forces a replay of the journal on next boot, lvm2-monitor does not shutdown cleanly on halt, various log entries contain "init[1]: Got invalid poll event on pipe." followed by e.g. "init[1]: Unit sys-kernel-security.automount entered failed state.", and there are several "mount" errors when systemd re-execs itself to apparently try to handle the busy inodes situation.
Some testing on F-14, some on rawhide. Seems to work ok, but there are some behavioral changes.
David Ramsey
Warning warn
[1] [2]
Warning warn
[3] [4]
  1. RHBZ #630914
  2. Was RHBZ #630915 now listed as RHBZ #630935
  3. RHBZ #631592
  4. RHBZ #631160

system's smolt data
He Rui
Warning warn rhe [1] [2]
none
  1. RHBZ #630914
  2. RHBZ #630915