| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Adam Williamson <awilliam@redhat.com>
|
|
|
|
|
|
|
| |
Also don't check out the tests if we're on master branch, but
have local modifications.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
|
|
|
|
|
| |
Might be better to do this with some other account, but uh, for
now...
|
|
|
|
|
| |
We need to create the ppc hard disk images from the ppc workers,
so they need rw access to the share.
|
|
|
|
| |
OK, this version actually seems to work.
|
|
|
|
|
| |
This reverts commit d6e32c9901c9f335a2fd2581dbaee1add9d1d9d0.
It didn't work.
|
|
|
|
| |
Seems like the config needs to be in the VirtualHost definition.
|
|
|
|
|
|
| |
Actually openQA playbook already includes the apache role, which
sets up the config file. The 404s are for some other reason. But
keep the comment change.
|
|
|
|
| |
This should stop collectd generating tons of 404 requests.
|
| |
|
|
|
|
|
|
|
|
| |
It does, sometimes, and that probably shouldn't stop the play.
We likely already have some older images, and even if this is
the *first* creation, we can go ahead with the rest of the
deployment safely enough, and debug the image creation problem
later.
|
| |
|
|
|
|
| |
Seems to be working fine in staging, so let's do it.
|
| |
|
|
|
|
| |
For now, just enable this on staging to check it works okay.
|
|
|
|
| |
Forgot these were in a separate file...
|
|
|
|
|
| |
We split fedora_openqa and createhdds out into their own repos,
this should adapt to the change (I hope).
|
|
|
|
|
| |
flippy flippy...u-t packages are untested, don't want them
getting to stable.
|
|
|
|
| |
Now it's master, not develop.
|
|
|
|
| |
We're moving stuff. Look out!
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The capability to handle a variance between prod and staging
here is just temporary while I'm testing the new fixed asset
handling stuff by deploying it on staging. Once it's tested
and merged we'll just have prod and staging do the same thing.
But for now we need to cleanly handle them having the static
disk images in different places.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've enhanced `createhdds check` to exit 1 if all images are
present but some are old, and 2 if any images are missing. We
use this to only create images if any are missing here in the
play; we rely on the daily cron job to rebuild old images.
This is kind of a band-aid for a weird issue on openqa01 where
virt-install runs just don't seem to work properly after the
box has been running for a while, so createhdds doesn't actually
work and any playbook run gets hung up on it for a long time.
This doesn't fix that, but does at least mean we can run the
playbook without being bothered by it. To get createhdds to run
properly and actually regenerate the outdated images, we have
to reboot the system and run it right away, it seems to work
fine right after the system boots up.
|
| |
|
|
|
|
|
| |
no longer needed since recent tweak to repository config in
tests.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
we need to install some additional packages for the revised
createhdds (but we no longer need pexpect), and ensure libvirtd
is running before running createhdds.
|
|
|
|
|
|
| |
it's not really fatal when it fails (except on first deployment)
and nothing else later depends on it, so we can go ahead and
continue the run even if it fails
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
instead of just relying on it getting run when we do an
ansible run, since that's intermittent and it's annoying
when you want to do an ansible run and it sits there for
hours creating disk images. This way we'll know they'll
get updated regularly and ansible runs should never get
blocked on image creation, though we still do it in the
ansible plays just in case (and for initial deployment).
This should now be safe, with the recent changes to make it
time out gracefully and run atomically. We also use withlock
to make sure we don't stack jobs.
|
|
|
|
|
|
|
| |
this will only work with the new openqa package builds I just
did, but won't break anything with older ones. With a new enough
openQA package, it'll prevent the web UI from showing download
links for ISOs and HDD files.
|
|
|
|
| |
without this, ARM tests do not run (phab T801)
|
|
|
|
|
| |
the COPR stuff is long gone so these weren't doing anything,
they just got left around by accident.
|
|
|
|
| |
srsly, what the hell.
|
|
|
|
|
|
| |
I tweaked the playbook to not patch the templates for non-infra
deployments, but then forgot to make test loading work using
non-patched templates for non-infra...
|
|
|
|
|
| |
rwmj has refreshed the i686 base image now, so let's try this
again.
|
|
|
|
|
|
|
|
|
|
|
|
| |
necessary updates for openqa roles have gone stable for now, so
disable updates-testing usage (keep the plays around commented,
though, since we'll likely need them again in future). Also, a
bit more attempted support for non-infra use: make the monkey
patching of the repo URLs in the test templates only happen if
deployment_type is defined, actually respect the openqa_consumer
var (don't enable the job scheduling consumer unless it's truey)
and only enable any wiki reporting consumer if deployment_type
is defined.
|
|
|
|
|
|
| |
This reverts commit 9872fe3fc8e7b03b345a278b58a58982b0ccb266.
Looks like the i686 base image hasn't been refreshed yet, so
i686 image generation still fails. Curses!
|
|
|
|
|
|
|
| |
rwmjones says the guestfs / rpm bug has been fixed (a new base
fedora-23 image has been uploaded which should avoid it, anyway)
so let's try turning disk image generation back on and see how
it flies.
|
|
|
|
|
| |
https://bugzilla.redhat.com/show_bug.cgi?id=1320754 is messing
it up. Disable for now so I can get other changes through.
|
|
|
|
|
|
|
|
| |
I'm still kinda trying to make the openqa roles usable outside
of infra, so now I have a minute, let's do this: it makes the
static UID/GID for geekotest optional and configurable, instead
of hard coding it. For infra we set the value to 601, as we
are already using, in the openqa and openqa-stg group config.
|
|
|
|
|
| |
just in case we wind up with multiple job groups, this should
be more correct.
|
| |
|
|
|
|
|
|
|
| |
this is a database value and there's no openQA API function to
set it, so we have to do it directly in the database...this
*should* work. I think. I should add equivalent functionality
for sqlite use as well, really...
|
|
|
|
|
|
|
|
|
| |
there seems to be a bug in python2-guestfs which causes the
disk image with an updates.img file to be broken (the updates
image is only 4096 bytes long and incomplete). When built with
Python 3 the image seems to be fine. So, run the script with
python3 (as its hashbang says) and ensure necessary packages
are installed.
|
| |
|
|
|
|
|
| |
I'd like to revise this a bit to be usable outside infra again,
but tomorrow...or later...
|