|Fedora Test Days|
|Mail • Subscribe • Archives|
What to Test?
Today's installment of Fedora Test Day will focus on Thermostat
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
Prerequisite for Test Day
- An updated Fedora 19 pre-release (physical machine or virtual machine), or a live image. Tips on using a live image are available at FedoraLiveCD.
- You will either need a physical machine or a virtual machine running a pre-release of Fedora 19
- Make sure that your system is up-to-date. You can update your system using the update manager.
- If you have a F19 installation, you should have the following packages installed:
You can download this build for your architecture from Koji and use
sudo yum localinstall thermostat-0.8.0-0.1.20130521hg97e66ed2e4ae.fc19*.rpm thermostat-webapp-0.8.0-0.1.20130521hg97e66ed2e4ae.fc19*.rpm in order to install it.
Please perform as many of the test cases listed as you have the time and the resources to complete, and fill out your results in the table below. You do not need a Fedora account to fill in the table. It is recommended to perform the tests in order, since some tests build on things explained in previous tests.
Note that thermostat consists of four (4) services. Each of which can be run on a different host. The first service is Thermostat storage (a.k.a. the database). The second one is the Thermostat webservice. This one has been introduced for security reasons. If you do not plan to use Thermostat in a distributed environment - or don't care about security - this service can probably be skipped. The third service is the Thermostat agent. It is a service which one needs to run on every host where JVMs should be monitored. The last component in this quartet are various forms of Thermostat clients.
As well as running the formal test cases, you can help simply by using Thermostat and/or Thermostat's Eclipse integration and report any problems you come across in the course of your typical use, even if they do not match up with any of the test cases. If unsure if something is a bug feel free to ask in #fedora-test-day.
If you have problems with any of the tests, try and report a bug. Thermostat bugs should be reported to Thermostat's Bugzilla. You will need an icedtea bugzilla account to report bugs for Thermostat. Creating one is easy, and we will help you do this if you ask in IRC.
If you are not sure of the appropriate component, please check in IRC before filing, there are many possibilities. 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 Results table 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, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to describe your result, following the examples in the Sample user row.
|User||Version||Storage||Logging||Agent||Service||Swing Client||Shell||Cmd Chan||Heap||Thread||Commands||Plug-in||Web Basic||Web Auth||Remote||References|
- Thermostat gui failed to start on one occasion but worked immediately after. paste.fedoraproject.org. "thermostat agent -d" also was not producing error output when unable to connect to tomcat, even with logging set up as described in earlier test case, and with error messages being produced and visible in tomcat logs.
- When I double click on a heap dump, the live VM starts using 100% cpu and becomes unresponsive. After ~5 minutes, the OOM killer kills the thermostat swing client
- Generally in the shell it was not very intuitive which ids to use for which commands. It would be nice to have a list of example usages somewhere + where can i find the ids, such as "If you want to create a heap dump you need an id of a _currently running_ vm, which can be found by list-vms. The typical call in the shell with minimal number of options is Thermostat> dump-heap -a ble123ble-very-long-id -v 4567 where -a is for specifying the host_id and -v for the vm_id."
- One more thing that surprised me in the shell was that if I run the sequence thermostat storage --start, thermostat agent (in another terminal), thermostat shell, then the connect -d ... command tries to connect to a db, whereas if I run some other command in the shell before the connect (e.g. list-vms) then this command autoconnects and subsequent call to connect tells me the connection already exists. (Maybe the side effects of commands could be noted somewhere.)
- on the live image i encountered a build failure: [ERROR] Failed to execute goal on project thermostat-plug-in-storage-common: Could not resolve dependencies for project com.redhat.thermostat.tutorial.kernel.cmdline:thermostat-plug-in-storage-common:bundle:0.0.2-SNAPSHOT: Failed to collect dependencies for [org.osgi:org.osgi.core:jar:4.2.0 (provided), org.osgi:org.osgi.compendium:jar:4.2.0 (provided), com.redhat.thermostat:thermostat-storage-core:jar:0.8.0-SNAPSHOT (compile), com.redhat.thermostat:thermostat-common-core:jar:0.8.0-SNAPSHOT (compile)]: Failed to read artifact descriptor for org.fusesource.jansi:jansi:jar:1.9: The repository system is offline but the artifact org.fusesource:fusesource-pom:pom:1.8 is not available in the local repository. -> [Help 1]
- Occasionally, after right clicking on the graph and then clicking "Heap Dump" more than once, the VM becomes unresponsive. Not 100% reproducible
- It is not very intuitive/obvious for average user that this feature starts working/displaying threads only after the red "Start Recording" is clicked