This is just cleaning up the mess of the bad parameter from
earlier, run of this play broke halfway through, need to do the
remaining half without choking on this part.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
For some reason here the bridge has a different mac address than the
interface that it's using to talk to the network.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This unifies prod and stg onto the ways of doing things for the
latest packages, and rejigs the swtpm stuff a bit to tear down
more (we shouldn't need the custom SELinux policy any more).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Right now we are running a special docker on osbs nodes that allows it
to actually work with f35+ containers. Without this glibc does a syscall
that docker doesn't understand and just blocks, breaking (at least) dns
resolution in the container. So, until we move these nodes from rhel7,
we are going to have to deal with this.
In addtion to excluding this, if it ever gets mistakenly upgraded, you
need to downgrade and then: remove
'--seccomp-profile=/etc/docker/seccomp.json \' from
/usr/lib/systemd/system/docker.service
do 'systemctl daemon-reload'
do 'systemctl restart docker'
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
These implications constraint us:
max-workers is used => cronolog needs to be used
log counter enabled => we need logrotate
But:
when logrotate is used => cronlog doesn't detect rotation
So the '4c4b63516d' is IMO explained.
Cronolog kept writing the log to the old descriptor, and the new
access.log link was just empty (before 4c4b63516d when we just
reloaded, not restarted). So I hope now that there isn't any other
problem that would require us to restart Lighty regularly.
The **UGLY** work-around is to terminate the cronlog process. As I've
found out, cronlog is automatically restarted by mod_accesslog - though
this is somewhat gray zone and we should long-term do one of those:
- stop using logrotate && rework log counter
- stop using max-workers && cronlog
- stop using Lighty
Resolves: https://pagure.io/copr/copr/issue/2001
Resolves: https://pagure.io/fedora-infrastructure/issue/10391
reg is putting a /static/ into asset path since it's upgrade.
Just alias it to / here to avoid the problem for now.
Hopefully we are going to be moving to quay.io and can stop caring about
it.
Fixes infra 10673
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We used to use btseed, but it stopped working and we couldn't sort out
why, so we switched to running rtorrent in a tmux instead. Its not
great, but it does work for a seeder.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
os-autoinst is actually an official build now, and this is a
newer (and somewhat fixed) openQA scratch.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
