Test Day:2014-09-16 Cockpit

Fedora Test Days
Cockpit Test Day
Date	2014-09-16
Time	all day
Website	QA/Fedora_21_test_days
IRC	#fedora-test-day (webirc)
Mailing list	cockpit-devel

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 user interface.

http://cockpit-project.org

Who's available

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), Patrick Uiterwijk (puiterwijk)
• Quality Assurance - Jan Ščotka (jscotka)

Prerequisite for Test Day

A machine that can run Fedora 21 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 21 Server. Make sure that your installation is recent enough. Either install Fedora 21 Server Alpha TC7 or run yum update in an older Fedora 21 Server installation. You should have at least Cockpit 0.23. In the Server variant of Fedora 21, Cockpit is enabled by default. For other variants, please refer to the Notes at the end of this page.
• Prepared Live ISO images: (root have no password here by default, anything you type will access cockpit page)
  • x86_64 - https://fedorapeople.org/groups/qa/20140916-Cockpit-Test-Day-Live-x86_64.iso
  • i386 (without Docker) - https://fedorapeople.org/groups/qa/20140916-Cockpit-Test-Day-Live-i386.iso
• Image for virt-manager : http://fedorapeople.org/groups/qa/20140916-Cockpit-VM-disk-image.qcow2.xz
  • user/password: test/test root/internal

curl https://fedorapeople.org/groups/qa/20140916-Cockpit-VM-disk-image.qcow2.xz >20140916-Cockpit-VM-disk-image.qcow2.xz
unxz 20140916-Cockpit-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=20140916-Cockpit-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 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". You can log into Cockpit as any user that exists on the machine, but currently only "root" has enough privileges to execute the test cases. Trying with any other user, even those that are in the "wheel" group, will likely lead to techno-babble error messages. (This will be improved as Cockpit and its dependencies evolve, of course.)

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.

Unfortunately, Cockpit is quite far from being finished. There are so many things worth improving that it will be a lot of work to report them all. For example, most of the dialogs don't do intelligent validation of user input. Thus, we can not ask you to be exhaustive. Feel free to report only things that you consider non-obvious´ or are particularily important to you.

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. 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

• Basic
  • Password change
  • Create user account

• Storage
  • Monitor disk I/O
  • Create a RAID Device
  • Create a Logical Volume

• Network
  • Monitor network I/O
  • Create VLAN
  • Create Bond

• Docker
  • Download and run image
  • Create a new image and run it

Test Results

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

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.

Basic

User	Hardware	Password change	Create user account	References
Alich	Hewlett-Packard HP xw4600 Workstation	pass	fail
jskladan	X230	pass	pass
lnie	virt-manager	pass	pass
baoboa	HP workstation Z400	pass	pass
jprokes	VPS	fail	pass
dspurek	Lenovo 440s (+VM)	fail	pass
roshi	virt-manager	pass	pass
psklenar	virt image	pass	pass
elemc	Gigabyte PH67-DS3-B3	pass	pass
lpol	openstack instances	pass	pass pass
jscotka	lenovo T61	pass	pass pass
omoris	Lenovo 430s (+VM)	pass	pass
rskvaril	Lenovo T440s	pass	pass
bblaskov	openstack	fail
alikins	f21-server-cockpit-virt-image		warn
konstantinjch	ASRock P67 Extreme4	pass	pass
pschindl	Lenovo ThinkPad T540p	pass	pass

Storage

User	Hardware	Monitor disk I/O	Create a RAID Device	Create a Logical Volume	References
Alich	Hewlett-Packard HP xw4600 Workstation	pass	pass	pass
jskladan	X230	pass	pass	pass
baoboa	HP workstation Z400	pass	pass	pass
jprokes	VPS	pass	pass	fail
roshi	virt-manager	pass	pass	pass
elemc	Gigabyte PH67-DS3-B3	pass	pass	pass
jscotka	lenovo T61	pass	pass	pass
rskvaril	Lenovo T440s	pass	pass	pass
alikins	f21-server-cockpit-virt-image		fail warn warn
konstantinjch	ASRock P67 Extreme4	pass	pass	pass
pschindl	Lenovo ThinkPad T540p	pass pass	warn	pass

Network

User	Hardware	Monitor network I/O	Create VLAN	Create Bond	References
jskladan	X230	pass	pass
baoboa	HP workstation Z400	pass	pass
jprokes	VPS	pass	pass	pass
todoleza	openstack/vps	fail
roshi	virt-manager	pass
elemc	Gigabyte PH67-DS3-B3	pass	pass	pass
jscotka	lenovo T61	pass	pass	pass
omoris	Lenovo 430s (+VM)	pass	pass	pass
rskvaril	Lenovo T440s	pass	pass
konstantinjch	ASRock P67 Extreme4	pass	pass	pass
pschindl	Lenovo ThinkPad T540p	pass

Docker

User	Hardware	Download and run image	Create a new image and run it	References
baoboa	HP workstation Z400	pass	pass
jprokes	VPS	pass pass	pass
dspurek	Lenovo 440s (+VM)	pass	pass
roshi	virt-manager	pass	pass
elemc	Gigabyte PH67-DS3-B3	pass	pass
lpol	openstack instances	pass	pass
jscotka	lenovo T61	pass	pass
omoris	Lenovo 430s (+VM)	pass	pass

Notes

We recommend that you install Fedora 21 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