#289: Missing autotest debug logs
----------------------+-----------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: autotest | Keywords:
----------------------+-----------------------------------------------------
I've found a test run where autotest debug logs are missing. What's wrong?
We need them.
http://autoqa.fedoraproject.org/results/72107-autotest/qa06.c.fedoraproject…
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/289>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#182: Write virt management script
----------------------------+-----------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Virtualization
Component: infrastructure | Version: 1.0
Keywords: |
----------------------------+-----------------------------------------------
We must write a virt management script that will be able to the basic
tasks for us:
* query for available virt systems that we can use
* switch between "real" disk and a disk snapshot for a virt system
* revert a disk snapshot for a virt system
* perform some command in a virt system - e.g. "yum update" for keeping
it periodically up-to-date
* install/reinstall a virt-system for us with specified distro
* (some more to come?)
We may want to use some pre-defined names syntax to recognize what virt
systems do we have. For example:
{{{
/dev/vg_autoqa/F12_i686_1
/dev/vg_autoqa/F12_i686_1-snap
}}}
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/182>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#254: Trasnfer autoqa library to autotest clients
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: autotest | Keywords:
-------------------------+--------------------------------------------------
Currently autotest clients do not require autotest package installed,
autotest server transfers all necessary files over rsync. But autotest
clients require autoqa installed (because of our autoqa libraries), which
in turn requires autotest.
This creates quite a lot of confusion where to edit which files when
testing new stuff. It would be much easier if we somehow transferred also
the autoqa library together with autotest files. Can we bend autotest a
little to rsync also our library to the client? Or, can we use similar
approach as copying the config files to the test directory also with
autoqa library? It would be great.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/254>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#196: Log failed job scheduling
-------------------------+--------------------------------------------------
Reporter: kparal | Owner: kparal
Type: enhancement | Status: new
Priority: major | Milestone:
Component: harness | Version: 1.0
Keywords: |
-------------------------+--------------------------------------------------
Currently when we schedule a job and it fails, we just print it out and
forget about it:
{{{
retval = schedule_job(control, email=email, name=testname,
required_arch=arch, dryrun=opts.dryrun,
labels=aq_labels)
if retval != 0:
print "ERROR: failed to schedule job %s" % testname
}}}
That should not be the case. We should:
* use syslog and log important stuff to /var/log/autoqa.log or similar
* send an email about failed scheduling to autoqa-results
That way we will know something is wrong and will be able to fix it.
Otherwise it just silently fails and we don't know about it.
Feel free to reassign the ticket if you want to work on it.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/196>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project