Test Day:2014-09-16 Cockpit

From FedoraProject

Jump to: navigation, search
Fedora Test Days
Echo-testing-48px.png
Cockpit Test Day

Date 2014-09-16
Time all day

Website QA/Fedora_21_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.

Contents

[edit] 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

[edit] Who's available

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

[edit] 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.

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.

[edit] 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.

[edit] Test Cases

[edit] 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.

[edit] Basic

User Hardware Password change Create user account References
Alich Hewlett-Packard HP xw4600 Workstation
Pass pass [1]
[2]
Fail fail [3]
  1. RHBZ #1142175
  2. Useless logout message
  3. RHBZ #1142234
jskladan X230
Pass pass
Pass pass
lnie virt-manager
Pass pass
Pass pass
baoboa HP workstation Z400
Pass pass
Pass pass
jprokes VPS
Fail fail [1]
[2]
Pass pass
  1. RHBZ #1142208
  2. Problem with password change on multiple servers managed by cockpit.
dspurek Lenovo 440s (+VM)
Fail fail [1]
[2]
Pass pass
  1. RHBZ #1142154
  2. unprivileged user can't change own password
roshi virt-manager
Pass pass
Pass pass
psklenar virt image
Pass pass [1] [2]
[3]
Pass pass
  1. RHBZ #1142210
  2. RHBZ #1135444
  3. selinux, random log out
elemc Gigabyte PH67-DS3-B3
Pass pass
Pass pass
lpol openstack instances
Pass pass
Pass pass [1] [2]
Pass pass
  1. RHBZ #1142229
  2. RHBZ #1142215
jscotka lenovo T61
Pass pass
Pass pass [1]
[2]
Pass pass [1]
[3][4]
  1. 1.0 1.1 RHBZ #1140562
  2. second trouble: https://github.com/cockpit-project/cockpit/issues/1160
  3. RHBZ #[[rhbug:|]]
  4. second trouble: https://github.com/cockpit-project/cockpit/issues/1160
omoris Lenovo 430s (+VM)
Pass pass
[1]
Pass pass
[2]
  1. Password field should be cleared when incorrect password is used to log-in.
  2. Not very helpful error messages when changing roles, terminating session or deleting when logged in as newly created user.
rskvaril Lenovo T440s
Pass pass
Pass pass
[1]
  1. user can't change own avatar
bblaskov openstack
Fail fail
[long 1]
alikins f21-server-cockpit-virt-image
Warning warn [1]
[2]
  1. RHBZ #1142426
  2. Extemely long "Real Name" for user account creation works, but causes display text wrapping issues.
konstantinjch ASRock P67 Extreme4
Pass pass
Pass pass
pschindl Lenovo ThinkPad T540p
Pass pass
Pass pass


[edit] Storage

User Hardware Monitor disk I/O Create a RAID Device Create a Logical Volume References
Alich Hewlett-Packard HP xw4600 Workstation
Pass pass
[1]
Pass pass [2]
Pass pass [3] [4]
  1. Graphs have no scale, some issues with live image on USB (data didn't follow reading/writing)
  2. RHBZ #1142396
  3. RHBZ #1144472
  4. RHBZ #1144481
jskladan X230
Pass pass
Pass pass
Pass pass
baoboa HP workstation Z400
Pass pass
Pass pass
Pass pass
jprokes VPS
Pass pass [1]
Pass pass [2]
Fail fail [3]
  1. RHBZ #1142228
  2. RHBZ #1142251
  3. RHBZ #1142297
roshi virt-manager
Pass pass
Pass pass
Pass pass
elemc Gigabyte PH67-DS3-B3
Pass pass
Pass pass
Pass pass
jscotka lenovo T61
Pass pass
Pass pass
Pass pass
rskvaril Lenovo T440s
Pass pass
Pass pass [1]
Pass pass
  1. RHBZ #1142248
alikins f21-server-cockpit-virt-image
Fail fail [1]
[2]
Warning warn
[long 2]
Warning warn [3]
[4]
  1. RHBZ #1142459
  2. Attempting to format a raid5 partition of loop devices that uses up all space fails mostly silently.
  3. RHBZ #1142443
  4. Works, but a cosmetic issue: available block devices are listed in lexical order, so that 'loop10' precedes 'loop2'
konstantinjch ASRock P67 Extreme4
Pass pass
Pass pass
Pass pass
pschindl Lenovo ThinkPad T540p
Pass pass
[1]
Pass pass
Warning warn [2]
Pass pass [3]
[4]
  1. When I hover over the graph nothing happens (step 4 in test case). Also graphs don't contain any information about scale.
  2. RHBZ #1142236
  3. RHBZ #1142259
  4. It was hard to set size which would fill the whole volume (step 3).


[edit] Network

User Hardware Monitor network I/O Create VLAN Create Bond References
jskladan X230
Pass pass
Pass pass
baoboa HP workstation Z400
Pass pass
Pass pass
jprokes VPS
Pass pass
Pass pass
[1]
Pass pass
  1. I didn't expect cidr format of netmask when the field for this is so long.
todoleza openstack/vps
Fail fail [1]
[2]
  1. RHBZ #1142798
  2. unmanaged NetworkManager dependency
roshi virt-manager
Pass pass
elemc Gigabyte PH67-DS3-B3
Pass pass
Pass pass
Pass pass
jscotka lenovo T61
Pass pass
Pass pass
Pass pass
omoris Lenovo 430s (+VM)
Pass pass
Pass pass
Pass pass
rskvaril Lenovo T440s
Pass pass
Pass pass
konstantinjch ASRock P67 Extreme4
Pass pass
Pass pass
Pass pass
pschindl Lenovo ThinkPad T540p
Pass pass


[edit] Docker

User Hardware Download and run image Create a new image and run it References
baoboa HP workstation Z400
Pass pass
Pass pass
jprokes VPS
Pass pass [1]
Pass pass
Pass pass
  1. RHBZ #1142362
dspurek Lenovo 440s (+VM)
Pass pass [1]
[2]
Pass pass
  1. RHBZ #1142209
  2. downloaded image disappears after click on another tab
roshi virt-manager
Pass pass
Pass pass
elemc Gigabyte PH67-DS3-B3
Pass pass
Pass pass
lpol openstack instances
Pass pass [1]
Pass pass
  1. RHBZ #1142129
jscotka lenovo T61
Pass pass
Pass pass
omoris Lenovo 430s (+VM)
Pass pass
Pass pass

[edit] 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

[edit] Long comments

  1. Some bugs which I found just by using cockpit (not relevant for this testcase) https://github.com/cockpit-project/cockpit/issues/1175 https://github.com/cockpit-project/cockpit/issues/1179 https://github.com/cockpit-project/cockpit/issues/1182
  2. Unclear if formatting needed to happen to the "Raid device" on the storage-detail page (Format is an option in it's drop down options) or the "Content" (defaults to "Format" option).