From Fedora Project Wiki

Revision as of 13:59, 23 March 2015 by Mvo (talk | contribs) (Notes)

Fedora Test Days
Echo-testing-48px.png
Cockpit Test Day

Date 2015-03-24
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.

What to test?

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

http://cockpit-project.org

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 : http://fedorapeople.org/groups/qa/xxxxx TODO
    • user/password: root/testvm testwheel/testwheel test/test
# 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 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
# sleep 60
# MAC=`virsh dumpxml cockpit | grep 'mac address' | cut -d\' -f2`
# IP=`cat /var/lib/libvirt/dnsmasq/default.leases |grep $MAC| head -1 | cut -d ' ' -f 3`
# echo "connect to http://$IP:9090 (user/password: root/testvm testwheel/testwheel test/test)"

How to test?

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

Important.png
Firefox 36.0 is known to choke on the Cockpit HTTPS certificates
See the end of this page for a workaround.
  • 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.

Basic

User Hardware Password change Create user account References
Stefw Lenovo laptop
Pass pass [1]
[2]
Fail fail [3]
  1. RHBZ #XXXXXXX
  2. Example entry
  3. RHBZ #1000000
Truong Anh Tuan Asus Laptop
Fail fail [1]
Pass pass
  1. RHBZ #1203632

Storage

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


Docker

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

Notes

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

Work around for Firefox certificate problem

If you are using Firefox 36.0 (and maybe also older versions), you might experience long delays and even crashes when connecting to Cockpit. See this bug report. You can work around this by executing the following command in the machine that runs Cockpit before connecting to Cockpit for the first time.

# cat >/etc/cockpit/ws-certs.d/~self-signed.cert <<EOF
-----BEGIN CERTIFICATE-----
MIIC/TCCAeWgAwIBAgIJANfhp4ZJBowrMA0GCSqGSIb3DQEBCwUAMBQxEjAQBgNV
BAMMCWxvY2FsaG9zdDAgFw0xNTAzMjMxMTM5MjdaGA8yMTE1MDIyNzExMzkyN1ow
FDESMBAGA1UEAwwJbG9jYWxob3N0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEAtU18jcd0jsptB4YEnEdDVHJtorkBz8jy/hVRToS1CBwCwATQ/QxSFCYV
ExSZSsHYLiojJoUoLcw8PKnUIql/3KudgV9h19gtjw8kvWxNV0NG0pDVoR+zrucP
z0+UelR+B8xGj6ZCa+8ts58SDktGXMNZEQH+CdnrIZzeR0jD1Wq2IZjhzX1QVf39
GGUQimVko6WppwhSrSkl0A9AHWO8aq1t4nibouCnQn2BDSB8r6kXD25gKiUDSo6y
tk4ZxBJ2+ReL9j7xw8oZ/2X6Xc57fxMPw1E1J03vPi67+apNNKZCRCluZrWkKYib
oBG+vESGKrXvudnx5UW2ilLugDHAAQIDAQABo1AwTjAdBgNVHQ4EFgQUaj6coA1S
jr6NQitVldnCSvJVgZIwHwYDVR0jBBgwFoAUaj6coA1Sjr6NQitVldnCSvJVgZIw
DAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQsFAAOCAQEALDA5xxQeeqkRCZPsivFF
Fj+mitWccCs+hayuRkVTw/oMtKbEYLqc1MjpUvm4uOGQGLoFWOBj7f3rss060A6q
qmuzy9CtWu6JpbLLcQXeWAPqXoCnRGc6zifev0Go60655EKJcrK0cEudXr636fNL
UVPbc4sQS2hwZYRSja1R0I0as+ZM/kzu/ZfOmwZtgismMPof0xVRGVXtS7/u5skB
6a7reHxRsU1oCM7Xu7Bh1iIjxWYJsTEN2l12lcMwB7U7jXoDfsFahEy+QEAMw8vo
8yWQRtb5IwTVog8mNbYFN53osR/sdhCSnDWDmaA4JiPeZUnFj8dYsg2WCUsRvb2i
/A==
-----END CERTIFICATE-----

-----BEGIN PRIVATE KEY-----
MIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQC1TXyNx3SOym0H
hgScR0NUcm2iuQHPyPL+FVFOhLUIHALABND9DFIUJhUTFJlKwdguKiMmhSgtzDw8
qdQiqX/cq52BX2HX2C2PDyS9bE1XQ0bSkNWhH7Ou5w/PT5R6VH4HzEaPpkJr7y2z
nxIOS0Zcw1kRAf4J2eshnN5HSMPVarYhmOHNfVBV/f0YZRCKZWSjpamnCFKtKSXQ
D0AdY7xqrW3ieJui4KdCfYENIHyvqRcPbmAqJQNKjrK2ThnEEnb5F4v2PvHDyhn/
Zfpdznt/Ew/DUTUnTe8+Lrv5qk00pkJEKW5mtaQpiJugEb68RIYqte+52fHlRbaK
Uu6AMcABAgMBAAECggEAGL11JKe2CRIoZKFuGaFD188xlMXoMGF8fx2LlcpYJb4k
xe0iU5WN0cAMmijybhgbltkbKNN80xsOkTyffQdiMkuc152bbWfLd70aR1rzBthg
XrVy4WTBETnol2KFoVfMRuYiLtICOFZQBzXKsfalqFzj14VNFC0Pf+u3DUUprAKD
vVzgzPcX9Ua5MJDIRjxgyIh41mGibaxkrAPB8EQp3oaBCYet7KmQT2sfZ9NegCaL
72RDK2YZb/KVjBrP+1X9yVEeJkD5rltkR6YUb8oEqEM1/521OmW03Nh6fjNBumFI
dkzPct3xS4vc7dOiSD75wEPz32D6QsIR8fEeiIfF0QKBgQDtAjIzsgazuMO94DW/
CDMR+KqK5RXoGLcMc8SHQbAEHZSpIOTtkdLo42e+ymb8lC2RQtlwuHV7xVjWCwdw
hdYwwqWLD8+yuW7bUUr2tzjTm5jpUP2E+o6W5cx17lOvJTttlbnqJJyZpKuI7UzF
C3iXmF4jI8T9Lo9HVKj61omChQKBgQDD1JWXz/OfYVoCGGHnl8L/MqGKIw+BahWv
bwA17GNObGcSj1jIpm/8609jMi91L6I44jBFarjPDgMffYzn/IpGohwG7fWlXjL6
lAu5xXzEa5/8Znv4FGOI75qZcLWSMOFnMypV3XeWV3y721DlFWFNFkJExril8XjI
dt8YoOrmTQKBgQC4fbgkY5Ux+0ZrnIdZ4AEZIS9oFTF7TRnYWJmIDAr++SPKj6+E
ernpzXLpolaOkK3z4EywoPXa1eD0JPuyjIwRwsLoP/OWlSAFGv+2kyNqHTnnjML7
66ppLhJ9TnrX4Kyk/iMNb1hzhSp92PKkg+xoXRQSWHqz9rVTekRblfrOnQKBgQCd
K6ZwdKdMOL8bxWP2kzgeyA0cqC0Oqg0Dg2xA2xuM2rYTEFeqmuJwtI8/xwyN2hAx
5V/mptPy4oUhJgwMOQTl0b/608t+0M7LjDyo+da8csCxu7MtlXeZdOy4z9v6nB6c
TFVjGt+bG1ZyE4Cmi/VPAFlph7C1Bsvw4G8H/kbpVQKBgFs/QR7Qd7t1YS8W7v52
KHv9j3KazwClv5I0hMb2jel9x6Ga3b1KT4WBVuVRCFDYOsrlPMWXu/FiqCzolsph
Mc2k1Tyfcx5whNtCT1uA+gRYQzPzlfxZPnJv52NyN04oun7m9GgkjEn4J57KWbah
CLYG1W8OBeOl2AhL4EXJ99lI
-----END PRIVATE KEY-----

EOF
# systemctl restart cockpit

Long comments