From Fedora Project Wiki

Fedora 21 Server Test Day
Echo-testing-48px.png

Date November 7th, 2014
Time all day

Website QA/Test_Days
IRC #fedora-test-day (webirc)

Mailing list
MailSubscribeArchives


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 and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

Today will be focusing on the major Server features: Rolekit, FreeIPA (the 'Domain Controller role'), Cockpit, and OpenLMI. We will be also testing for basic functionality. Please submit your findings to the table below.

Who's available[edit]

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

Requirements for testing[edit]

Getting the test image[edit]

We are using the Fedora 21 Final TC1 images as the reference testing images. You can find them here:

How to test?[edit]

  • Download the image for your architecture
  • Verify the download using the CHECKSUM file in the download directory
  • Install the image to your test system (refer to the Installation Guide for installation instructions)
  • Run the test cases linked in the result table below
  • File bug reports for any bugs you encounter
  • Add your results to the table

What to test?[edit]

For this Test Day, we will be running the test cases found in the following categories:

  1. Base Test Cases
  2. Rolekit Test Case
  3. FreeIPA Test Cases
  4. Realmd Test Cases
  5. Docker Base Setup Test Case
  6. Cockpit Test Cases (TC's Derived from Cockpit's Test Day)


Test Results[edit]

If you have problems with any of the tests, report a bug to Bugzilla usually for the relevant component - e.g. cockpit, or rolekit.

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, use the result template to enter your result, as shown in the example result line.

User Base Test Cases Rolekit Test Case FreeIPA Test Cases Realmd Test Cases Docker Base Setup Cockpit Test Cases References
Sample User
none
none
none
Pass pass
Warning warn [1]
Fail fail [2]
  1. RHBZ #54321
  2. RHBZ #12345
User:New[1]
none
none
none
none
none
none
  1. Copy/Paste this row to create a new one
User:satellit
Pass pass
[1]
none
none
none
none
none
  1. base initial setup -netinstall req root pswd setup in anaconda to finish * login to root - No firstboot
User:potty
Pass pass
[1]
Warning warn
[2]
none
none
Pass pass
[3]
Pass pass
[4]
  1. No problems.
  2. First deployment ended with "Error: COMMAND_FAILED: 256". Then, I decommission and deploy it again. After that, no problems.
  3. No problems.
  4. No problems.
User:junland
Pass pass
[1]
none
none
none
Pass pass
[2]
Pass pass
[3]
  1. All base tests went smoothly
  2. Did a basic run through the steps, downloaded multiple images and ran them. All seemed to be going well.
  3. Used Firefox on a another VM to access Cockpit and do tests. Made a RAID5 Array, VLAN, New User, Bonding interfaces and other tests.
User:Roshi
Pass pass
Warning warn
[long 1]
none
none
none
none
pwhalen
Pass pass
Fail fail [1]
[2]
none
none
none
Warning warn
[long 2]
  1. RHBZ #1153746
  2. As noted, first run 'Error: COMMAND_FAILED: 256' , when trying to redeploy 'Error: UNKNOWN_SETTING: admin_password'

Long comments[edit]

  1. First run ended with "Error: COMMAND_FAILED: 256" and after decommissioning and deploying again, 'rolectl list instances' reports: Error: The name :1.161 was not provided by any .service files'
  2. Cockpit reports storage incorrectly (web interface reports 4.1G, actual 9.9G total size). Network bonding not possible on device. Docker not suported.