Editing Test Day:2015-03-24 Cockpit

{{Infobox_group
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_22_test_days]]
| caption = Cockpit Test Day
| date = 2015-03-24
| time = all day
| website = [[QA/Fedora_21_test_days]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| fedora_mailing_list = cockpit-devel
}}

{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|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 ...
* Development - [[User:Stefw|Stef Walter]] (stefw), [[User:Mvo|Marius Vollmer]] (mvollmer), [[User:Andreasn|Andreas Nilsson]] (andreasn), Dominik Perpeet (dperpeet), Peter Volpe (pvolpe)
* Quality Assurance - [[User:jscotka|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 [https://getfedora.org/en/server/prerelease/ Fedora 22 Server Alpha] or run <code>yum update</code> 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 ''' : [https://fedorapeople.org/groups/qa/test_days/cockpit-test-day-i686.iso i686 ISO] [https://fedorapeople.org/groups/qa/test_days/cockpit-test-day-x86_64.iso x86_64 ISO]
** user/password: root/testvm
* '''Image for virt-manager''' : https://fedorapeople.org/groups/qa/test_days/fedora22-cockpit-x86_64.qcow2.xz
** user/password: root/testvm testwheel/testwheel test/test
<pre>
# curl https://fedorapeople.org/groups/qa/test_days/fedora22-cockpit-x86_64.qcow2.xz > fedora22-cockpit-x86_64.qcow2.xz
# unxz fedora22-cockpit-x86_64.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=fedora22-cockpit-x86_64.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)"
</pre>

== How to test? ==

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

{{admon/important|Firefox 36.0 is known to choke on the HTTPS certificates created by Cockpit 0.44 and earlier.|See the end of this page for a workaround.}}

{{admon/important|The firewall might or might not be open for Cockpit.|See the end of this page for details.}}

* Point a browser at '''<code>http:</code><code>//<server-ip-address>:9090</code>'''.
* Cockpit's login page will load.
* Cockpit uses a self-signed certificate, and your browser will very likely warn you about it. 

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

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 [http://github.org/cockpit-project/cockpit/issues Github] or in [http://bugzilla.redhat.com/enter_bug.cgi?component=cockpit&product=Fedora&version=21 Bugzilla].

== Test Cases ==

* '''Basic'''
** [[QA:Testcase Cockpit Account|Create user account]]
** [[QA:Testcase Cockpit Terminal|Use the command line]]

* '''Storage'''
** [[QA:Testcase Cockpit DiskIO|Monitor disk I/O]]
** [[QA:Testcase Cockpit RAID|Create a RAID Device]]
** [[QA:Testcase Cockpit LVM|Create a Logical Volume]]

* '''Network'''
** [[QA:Testcase Cockpit NetworkIO|Monitor network I/O]]
** [[QA:Testcase Cockpit VLAN|Create VLAN]]
** [[QA:Testcase Cockpit Bond|Create Bond]]

* '''Docker'''
** [[QA:Testcase Cockpit DockerImage|Download and run image]]
** [[QA:Testcase Cockpit DockerCommit|Create a new image and run it]]

== Test Results ==

If you have problems with any of the tests, report a bug either on [http://github.org/cockpit-project/cockpit/issues Github] or in [http://bugzilla.redhat.com/enter_bug.cgi?component=cockpit&product=Fedora&version=22 Bugzilla].

{{admon/important|For reporting results use primarily fedora testday app}}
'''[http://209.132.184.193/testdays/show_event?event_id=24 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 [[Template:result|result template]] to enter your result, as shown in the example result line.

=== Basic ===

{|
! User
! Hardware
! [http://fedoraproject.org/wiki/QA:Testcase_Cockpit_Login Password change]
! [http://fedoraproject.org/wiki/QA:Testcase_Cockpit_Account Create user account]
! References
|-
| [[User:Stefw|Stefw]]
| Lenovo laptop
| {{result|pass||XXXXXXX}}<ref>Example entry</ref>
| {{result|fail||1000000}}
| <references/>
|-
| [[User:Tuanta|Truong Anh Tuan]]
| Asus Laptop
| {{result|fail||1203632}}
| {{result|pass||}}
| <references/>
|-
|}

=== Storage ===

{|
! User
! Hardware
! [http://fedoraproject.org/wiki/QA:Testcase_Cockpit_DiskIO Monitor disk I/O]
! [http://fedoraproject.org/wiki/QA:Testcase_Cockpit_RAID Create a RAID Device]
! [http://fedoraproject.org/wiki/QA:Testcase_Cockpit_LVM Create a Logical Volume]
! References
|-
| [[User:Stefw|Stef Walter]]
| Lenovo Laptop
| {{result|pass}}  <ref>Test entry</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
|}


=== Docker ===

{|
! User
! Hardware
! [http://fedoraproject.org/wiki/QA:Testcase_Cockpit_DockerImage Download and run image]
! [http://fedoraproject.org/wiki/QA:Testcase_Cockpit_DockerCommit Create a new image and run it]
! References
|-
| [[User:Stefw|Stef Walter]]
| Lenovo Laptop
| {{result|pass}}  
| {{result|pass}}  
| <references/>
|}

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

<pre>
# dnf install cockpit
# firewall-cmd --permanent --add-service cockpit
# firewall-cmd --add-service cockpit
# systemctl start cockpit.socket
# systemctl enable cockpit.socket
</pre>

=== 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 [https://bugzilla.redhat.com/show_bug.cgi?id=1204670 this bug report].  You can work around this by executing the following commands in the machine that runs Cockpit '''before''' connecting to Cockpit for the first time.
<pre>
# cd /tmp
# openssl req -x509 -days 36500 -newkey rsa:2048 -keyout KEY -keyform PEM -nodes -out CERT -outform PEM -subj /CN=localhost
# cat CERT KEY >/etc/cockpit/ws-certs.d/~self-signed.cert
# rm CERT KEY
# systemctl restart cockpit
</pre>

=== Opending the firewall for Cockpit ===

Depending on how you have installed Cockpit, the firewall might or might not be open for it.  If you install Fedora Server, it should be open, but it currently is not.  See [https://bugzilla.redhat.com/show_bug.cgi?id=1204739 this bug].

In any case, execute the following commands to open it.
<pre>
# firewall-cmd --add-service cockpit
# firewall-cmd --permanent --add-service cockpit
</pre>
The effect is immediate, you don't need to restart Cockpit.

== Long comments ==
<references group="long" />

[[Category:Fedora 22 Test Days|c]]