|Fedora Test Days|
|Cockpit Test Day|
|Mail • Subscribe • Archives|
What to test?
Today's installment of Fedora Test Day will focus on testing Cockpit. Cockpit is a server admin interface.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Stef Walter (stefw), Marius Vollmer (mvollmer), Andreas Nilsson (andreasn), Dominik Perpeet (dperpeet), Peter Volpe (pvolpe)
- Quality Assurance - Jan Ščotka (jscotka)
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 updatein 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.
- Image for virt-manager : http://fedorapeople.org/groups/qa/xxxxx TODO
- user/password: test/test root/internal
# curl https://fedorapeople.org/groups/qa/xxxxx > 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 1024 -n cockpit --os-type=linux --os-variant=fedora20 --disk path=xxxx-VM-disk-image.qcow2,device=disk,format=qcow2 --vcpus=1 --vnc --noautoconsole --import # virt-manager &
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.
- Point a browser at
- Cockpit's login page will load.
- Cockpit uses a self-signed certificate, and your browser will very likely warn you about it.
<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
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!
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|
|Truong Anh Tuan||Asus Laptop||
|User||Hardware||Monitor disk I/O||Create a RAID Device||Create a Logical Volume||References|
|Stef Walter||Lenovo Laptop||
|User||Hardware||Download and run image||Create a new image and run it||References|
|Stef Walter||Lenovo Laptop||
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