From Fedora Project Wiki

Revision as of 13:22, 23 March 2015 by Jscotka (talk | contribs) (Prerequisite for Test Day)

Fedora Test Days
Cockpit Test Day

Date 2015-03-24
Time all day

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

Mailing list

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?

Today's installment of Fedora Test Day will focus on testing Cockpit. Cockpit is a server admin interface.

Who's available

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

Prerequisite for Test Day

A machine that can run Fedora 22 and that you can screw around with. This can be a virtual machine, but we are also very interested in test results on real hardware.

The test machine should ideally have multiple disks and multiple network interfaces. If you use a virtual machine, just add some virtual disks and network adapters.

  • Install Fedora 22 Server. Make sure that your installation is recent enough. Either install Fedora 22 Server Alpha or run yum update in an older Fedora 22 Server installation. You should have at least Cockpit 0.44. In the Server variant of Fedora 22, Cockpit is enabled by default. For other variants, please refer to the Notes at the end of this page.
  • LiveDVD  : i386 ISO x86_64 ISO
    • user/password: root/testvm
  • Image for virt-manager : TODO
    • user/password: root/testvm testwheel/testwheel test/test
# curl > xxxx-VM-disk-image.qcow2.xz
# unxz xxxx-VM-disk-image.qcow2.xz
# yum -y install qemu\*
# systemctl  restart libvirtd
# virt-install --connect qemu:///system --ram 2048 -n cockpit --os-type=linux --os-variant=fedora20 --disk path=xxxx-VM-disk-image.qcow2,device=disk,format=qcow2 --vcpus=1 --vnc --noautoconsole --import
# virsh start cockpit
# sleep 60
# MAC=`virsh -c qemu:///system dumpxml cockpit | grep 'mac address' | cut -d\' -f2`
# IP=`virsh -c qemu:///system net-dumpxml default | grep "MAC" |sed -r 's/.*ip=.([0-9.]*).*/\1/'`
# echo "connect to http://$IP:9090 (user/password: root/testvm testwheel/testwheel test/test)

Note that Docker is not enabled by default, but the test cases will tell you how to enable it.

How to test?

After boot, Cockpit is up and running and listens on port 9090.

Firefox 36.0 is known to choke on the Cockpit HTTPS certificates
See the next paragraph for a workaround.

If you are using Firefox 36.0 (and maybe also older versions), you might experience long delays and even crashed when connecting to Firefox. See this bug report. You can work around this by copying this file to /etc/cockpit/ws-certs.d/~self-signed.cert and then executing systemctl restart cockpit.

  • Run firewall-cmd --add-service cockpit; firewall-cmd --permanent --add-service cockpit to open the firewall for Cockpit.
  • Point a browser at http://<server-ip-address>:9090.
  • Cockpit's login page will load.
  • Cockpit uses a self-signed certificate, and your browser will very likely warn you about it.

(Here, <server-ip-address> is the IP address of your machine. You can find it by logging into the machine on the text console as "root" and running ip addr.)

Once the Cockpit log in screen is loaded in your browser, log in as "root" or some other user in the "wheel" group. You can log into Cockpit as any user that exists on the machine, but only "root" or "wheel" members have enough privileges to execute the test cases.

The test cases are intentionally a bit vague. They don't tell you exactly what button to click, and what to type into which field. You have to figure that out yourself! :-) Cockpit should be `discoverable´, and your feedback about this is very valuable.

The test cases don't cover every feature of Cockpit. Please stray from the test cases into whatever corner of Cockpit you want to explore!

When Cockpit encounters an internal error, a red "Oops" label will appear at the top right. Please report it when this happens. Look in the javascript console (Ctrl-Shift-J) for details. It is not a good idea to continue using Cockpit after an "Oops", but simply reloading the page should put you back on track.

Please report your feedback either on Github or in Bugzilla.

Test Cases

Test Results

If you have problems with any of the tests, report a bug either on Github or in Bugzilla.

For reporting results use primary fedora testday app

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 tables 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 Hardware Password change Create user account References
Stefw Lenovo laptop
Pass pass [1]
Fail fail [3]
  2. Example entry
  3. RHBZ #1000000
Truong Anh Tuan Asus Laptop
Fail fail [1]
Pass pass
  1. RHBZ #1203632


User Hardware Monitor disk I/O Create a RAID Device Create a Logical Volume References
Stef Walter Lenovo Laptop
Pass pass
Pass pass
Pass pass
  1. Test entry


User Hardware Download and run image Create a new image and run it References
Stef Walter Lenovo Laptop
Pass pass
Pass pass


We recommend that you install Fedora 22 Server since we would like you to also test whether Cockpit really works out of the box. Of course, if you would like to test Cockpit but would rather not go through the trouble of installing Fedora from scratch yet one more time, you can also add Cockpit to your existing Fedora system.

# yum -y install cockpit docker-io fedora-dockerfiles wmdocker
# firewall-cmd --permanent --add-service=cockpit
# systemctl reload firewalld.service
# systemctl start cockpit.socket
# systemctl enable cockpit.socket

Long comments