Per upstream koji folks we want to move the is_child_task to nearly the
top so child tasks get the right channel assigned. Also, we want to
make sure the ci and secure-boot rules only apply to build method.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Set the systemd-boot package to build on secure-boot channel and set all
the normal permissions for that that other secure-boot builds have.
Add the systemd-boot cert to pesign config so it can be signed by the
right cert.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
I got claude to dig into the things we tried to fix this issue and look
for things we missed. It found a few things:
1. In commit 35a1b3223b Victor Koycheff added some proxyopts for
keepalive, etc. However, unfortunately, while the variable was set
the template wasn't looking at that, so they were never actually
set in the website. ;( So, we fix that by passing the variable in the
right template here.
2. kojihub didn't have a keepalive set on the backend. (but this is
likely cosmetic since the problem is at the proxy layer). We fix
this by adding one anyhow.
3. The pass thru anubis didn't have keepalive set right, so we do
that in the template. This may fix other 502 issues with other
applications also.
Calude used 57,508 tokens looking at all this. ;)
Assisted-By: claude
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This acts as the second half of the fix for the 502 Bad Gateway errors
on long-running koji connections.
Fixes#12913
Signed-off-by: Victor Koycheff <victorkoycheff@gmail.com>
We don't want to move all packit builds, because it does a lot of
official builds for maintainers. Instead, we want to just move the
scratch builds over to the ci channel.
See: infra/tickets#13069
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
The current updates policy has the same rules for Branched after
Beta freeze / updates-testing activation as for stable releases,
so we don't need a specific Branched policy after that point at
all. It only needs to exist for the 'preenable' state. The
'current' state is useless, so get rid of it.
The Koji config handling was actually rather wrong in a few ways.
If we ever got into a situation where FedoraBranched was true
and FedoraBranchedBodhi was 'current', we'd allow block on the
branch, which seems bad. Also, because this block wasn't
conditionalized on FedoraBranched and FedoraBranchedNumber is
0 when FedoraBranched is false, we wound up defining a policy for
tag 'f0', which is also dumb (but probably harmless). Getting
rid of 'current' solves the first, conditionalizing the policy
on FedoraBranched solves the second.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
See https://pagure.io/fedora-infrastructure/issue/12995
We want to be careful adding anything here, but the same reasons we add
chromium are in play here. There's no ppc64le or s390x builds, so it
will just affect aarch64 and x86_64 where we have a lot of hosts in
heavybuilder channel.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This is part of an approved change [1] to remove `koji-osbuild` from
Fedora's Koji instances. In this commit the Koji configuration is
changed to no longer serve `osbuildImage` tasks in web or hub.
The `koji-osbuild` plugin has been replaced previously with the
`koji-image-builder` plugin which, instead of talking to a remotely
hosted service, builds images on Koji builders themselves.
All users of `koji-osbuild` have been migrated to `koji-image-builder`
and no builds are being scheduled that need to be handled by
`koji-osbuild` anymore.
[1]: https://fedoraproject.org/wiki/Changes/KojiServiceImageBuilderRemoval
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
We need to set this the same as the proxies so we don't have a keepalive
on the proxies that gets cut off my the lower limit on the hubs.
This may fix the 502 error with watch-tasks/watch-logs
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This introduces a set of variables for managing infrastructure changes
as EPEL minor versions change over time. This should drastically
simplify our changes during EPEL mass branching. This also drops the
earlier attempt of EPELCycleNumber and EPELBootstrapNumber variables,
which are no longer used.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
On riscv we don't want to do generic tasks that can be done on any arch
on riscv builders. We want those to go to the x86_64 builders that are
much faster.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
The riscv koji isn't using a seperate kojipkgs, so it's like staging and
should just serve repos/etc by itself.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Enables the `image-builder` plugin from `koji-image-builder` in the
production environment for both the koji hub, and the koji builder
(kojid).
This is based on the earlier enablement in staging where I've
succesfully tested some builds and it didn't seem to bring down all of
the staging instance.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
Enables the `image-builder` plugin from `koji-image-builder` in the
staging environment for both the koji hub, and the koji builder (kojid).
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
