| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
| |
...by extending the fedmsg consumer config file. Requires the
latest openqa_fedora_tools to work.
|
|
|
|
|
|
|
|
| |
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...
|
|
|
|
| |
apparently the policy.py file shouldn't cause any problems.
|
|
|
|
| |
let's start over and see where we're at.
|
|
|
|
|
|
| |
seems like we need the internal inbound relay but the public
outbound relay? I don't even know...but we definitely can't
connect to busgateway01.phx2.fedoraproject.org:3999
|
|
|
|
|
|
|
| |
i think the relay 'fix' is only needed for stg, because there
was a firewall rule added for prod but not stg. It's not really
a 'fix' either (it'll stop messages getting out) but it at
least prevents fedmsg-relay failing, so keep it for now.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Ralph *mostly* fixed it, but the config we get from fedmsg/base
still doesn't quite work, so this just hacks it up after that
role's done. This will go away with a couple more fixes to the
fedmsg/base role.
|
| |
|
|
|
|
|
| |
we need some from updates-testing for now. also, we need
openqa-httpd for the server.
|
| |
|
| |
|
| |
|
|
|
|
| |
Well hey, let's hope this works!
|
|
|
|
| |
we only needed it once.
|
| |
|
| |
|
|
|
|
|
| |
ditch the old systemd consumer service, install the fedmsg
consumer config file, add some fedmsg-hub reload notifications.
|
|
|
|
|
|
| |
with openQA jobs being scheduled and wiki results reported
(well, when we get that working again) by fedmsg-hub consumers,
we have to let the fedmsg user read these files.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
...otherwise you end up scheduling jobs with stale code and
they fail, NOT THAT THAT'S EVER HAPPENED TO ME
|
| |
|
| |
|
| |
|
|
|
|
|
| |
mainly systemd unit changes, clean up the old ones, enable the
new.
|
| |
|
|
|
|
|
| |
all required packages except openqa itself are now in main repo,
openqa is in infra repo.
|
| |
|
|
|
|
| |
we moved the openqa scheduler within the git checkout.
|
| |
|
| |
|
| |
|
|
|
|
| |
this step uses && and >, needs a shell.
|
|
|
|
|
|
|
|
|
|
|
|
| |
we really shouldn't always_run these, as they actually *do*
stuff. That does mean that in check mode we won't check if
database init and admin user creation are necessary, but these
are only ever necessary exactly one time at initial deployment
which is likely to be kicked off manually anyway, so it should
not be a problem. We adjust the 'when' condition for the 'wait
for services to start up' action, so it will work in check mode
with the 'services' variable undefined (because the step that
defines it now won't be run).
|
|
|
|
|
| |
it causes problems (prevents updated code being installed) and
is not necessary (git module supports check).
|
| |
|
| |
|
|
|
|
| |
and install the additional deps.
|
|
|
|
| |
the servers have nested virt enabled now, so this should be OK
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This puts in place the bits needed to use the new createhdds.py
for image generation, which works much nicer with ansible than
the old createhdds.sh. For now, the disk creation step is
disabled, because creating some images (including the ones that
get refreshed regularly) requires running VMs, and the openqa
server hosts are VMs themselves and do not currently have nested
virt enabled, so the creation would run extremely slow. Once we
get nested virt enabled, I'll change the condition for the image
creation step to what it should be. Until then I'll carry on
handling image creation manually (both hosts have all the images
at present anyhow).
|