Test Day:2010-09-07 Systemd

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Test Results)
(Install additional updates)
Line 38: Line 38:
 
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 wish to test using the live CD, a custom live CD for this event which includes the following updates is currently being created and this page will be updated when it is available.
 
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 wish to test using the live CD, a custom live CD for this event which includes the following updates is currently being created and this page will be updated when it is available.
  
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=193591 systemd-9-3.fc14]
+
From koji:
 +
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=193591 systemd-9-3.fc14]  
 
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=193588 initscripts-9.18-1.fc14]
 
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=193588 initscripts-9.18-1.fc14]
 
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=193903 dbus-1.4.0-1.fc14]
 
* [http://koji.fedoraproject.org/koji/buildinfo?buildID=193903 dbus-1.4.0-1.fc14]

Revision as of 16:34, 7 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

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

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 here. 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 wish to test using the live CD, a custom live CD for this event which includes the following updates is currently being created and this page will be updated when it is available.

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!