[AutoQA] #251: Move autotest applications into /usr/*bin
by fedora-badges
#251: Move autotest applications into /usr/*bin
-----------------------+----------------------------------------------------
Reporter: jlaska | Owner:
Type: task | Status: new
Priority: minor | Milestone: Packaging, Review, & Deployment
Component: packaging | Keywords:
-----------------------+----------------------------------------------------
The autotest package should supply binaries in /usr/bin/ ... so we can
rely on PATH and not have to call autotest with the full-path
(/usr/share/autotest/client/bin/autotest) when scheduling jobs in
'/usr/bin/autoqa'.
Alternatively, the autotest package could drop a script that updates PATH
appropriately into /etc/profile.d/autotest. But yuck.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/251>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
11 years, 6 months
[AutoQA] #157: conflicts: requested arch not respected
by fedora-badges
#157: conflicts: requested arch not respected
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
This is a bug in the potential_conflict.py script in tests/conflicts/.
Usage suggests using --arch options for specifying requested architecture
to be tested. But if you look at the attached log, the first and second
output match (that's correct), but the third doesn't match, even though it
should. Everything was tested on x86_64 machine.
Also from the usage line it is not clear whether --arch is related only to
particular yum repository selection (replacing $basearch keyword), or
whether it also relates to packages built for one architecture but being
in different repo (e.g. i686 packages are very often in x86_64 repo).
I have looked into the source code of the script and it seems that the
--arch option is not used at all, just printed out in the usage help??
Seth, you're listed as script author. Any comments on that? Thanks.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/157>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
11 years, 8 months
[AutoQA] #206: Update bodhi to enforce Package Update Acceptance policy
by fedora-badges
#206: Update bodhi to enforce Package Update Acceptance policy
----------------------------+-----------------------------------------------
Reporter: wwoods | Owner:
Type: task | Status: new
Priority: major | Milestone: Package Update Acceptance Test Plan
Component: infrastructure | Version: 1.0
Keywords: |
----------------------------+-----------------------------------------------
In order to enforce the Package Update Acceptance Test Plan, Bodhi will
need be modified to reject the push of any package that fails acceptance
testing.
The acceptance tests may need to send status/data to bodhi in order for it
to make decisions about policy (see e.g. ticket #205). Later bodhi might
just get data from resultdb (see that milestone for details).
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/206>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years
[AutoQA] #252: Provide all autotest client combinations that we need
by fedora-badges
#252: Provide all autotest client combinations that we need
------------------------+---------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.5.0
Component: production | Keywords:
------------------------+---------------------------------------------------
Currently our production server at http://autoqa.fedoraproject.org/ has 6
autotest clients assigned, all bare metals with Fedora 13 installed, with
mixed architectures. But we need more.
According to https://fedoraproject.org/wiki/Managing_autotest_labels we
have two architecture labels, two fedora release labels (the two currently
supported Fedora releases, I would omit Rawhide for now) and two virt
labels (virtual machine or bare metal). We need machines for every
combination of those labels (that is 8 IICC - if I count correctly). And
we would like to see a bit more 64bit machines, because we use them for
noarch tests.
Currently the only test that really requires all those combinations is
initscripts test. But there will be more in the future. It is quite some
farm, but it seems we'll have to build it.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/252>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 1 month
[AutoQA] #255: Use Config class to simplify access to configuration options
by fedora-badges
#255: Use Config class to simplify access to configuration options
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: minor | Milestone:
Component: core | Keywords:
--------------------+-------------------------------------------------------
Currently all our libraries and tests use ConfigParser and parse our
configuration files (autoqa.conf, fas.conf, etc) directly. That is not
ideal, it involves many lines of code, converting to correct variable
types (int, bool), handling default values, and so on.
We should create a Python class Config, which is initialized once in the
beginning, and then can be access globally and easily from any other
module. It will handle default values and type conversion centrally in one
place. Also access will be much easier.
PS: We already have autoqa.config module. Maybe we just don't use it?
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/255>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 1 month
[AutoQA] #194: Incorporate automated anaconda storage suite
by fedora-badges
#194: Incorporate automated anaconda storage suite
--------------------+-------------------------------------------------------
Reporter: jlaska | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
Chris Lumens has developed a virt-based test suite to automate different
disk/storage install scenarios. I've discussed this briefly with Chris,
but I'd be interested in seeing his test suite incorporated within autoqa
and run on a regular interval (perhaps along-side Liam's install tests).
The tests are currently available at http://clumens.fedorapeople.org
/anaconda-storage-test/
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/194>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 1 month
[AutoQA] #182: Write virt management script
by fedora-badges
#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
12 years, 5 months
[AutoQA] #254: Trasnfer autoqa library to autotest clients
by fedora-badges
#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
12 years, 5 months