james commented on pull request infra/ansible#3312 2026-04-28 05:08:48 +00:00
blockerbugs: remove deploymentconfig from playbook

+1

james commented on issue infra/tickets#13290 2026-04-27 19:08:15 +00:00
Request for account deactivation / username change guidance

Looks like there's nothing to do here, for infra.

james closed issue infra/tickets#13290 2026-04-27 19:08:15 +00:00
Request for account deactivation / username change guidance
james commented on issue infra/tickets#13278 2026-04-26 21:32:58 +00:00
Builds on buildhw-x86-13 stuck with "[Errno 11] Resource temporarily unavailable" errors

Still doing that task: 2026-04-26 21:29:40,693 [INFO] koji.TaskManager: open task: {'id': 144853101, 'waiting': None, 'weight': 1.9114358747916667}

james commented on pull request infra/ansible#3307 2026-04-24 16:11:30 +00:00
Fix the source and target reporting in openshift/object

I think it'd be better to leave the variables in the task name, otherwise you get a bunch of "Copying a file to /blah" which looks annoying. Having:

james commented on pull request infra/ansible#3308 2026-04-24 15:57:04 +00:00
blockerbugs: add Forgejo vars to deploymentconfig as well

This is just adding vars, so I don't see how it could break anything? But openshift is very special.

james commented on pull request infra/ansible#3302 2026-04-23 20:08:14 +00:00
Apply restrictive robots.txt to riscv-koji

+1

james commented on pull request infra/ansible#3301 2026-04-23 19:53:57 +00:00
Put riscv Koji behind anubis

Sure, try it ... worth noting that http://www.semrush.com/bot.html is hitting a bunch of URLs and we disallow all bots.

james commented on issue infra/tickets#13285 2026-04-23 19:07:11 +00:00
Enabling some monitoring for Fedora-CI

Really not sure how easy this is to integrate into zabbix ... Doesn't seem like the normal things we monitor, so 5 might not be enough.

james closed issue infra/tickets#13279 2026-04-22 23:22:20 +00:00
Signing problem with the latest rawhide kernels
james commented on issue infra/tickets#13279 2026-04-22 19:22:13 +00:00
Signing problem with the latest rawhide kernels

Okay, what we did/know:

james commented on issue infra/tickets#13282 2026-04-22 15:15:42 +00:00
New FAS Group: Fedora Matrix WG

I just tried to do this, but don't have permissions, SOP is here: https://docs.fedoraproject.org/en-US/infra/howtos/groups_in_fedora/#_how_to_create_a_group

james commented on issue infra/tickets#13279 2026-04-21 22:08:40 +00:00
Signing problem with the latest rawhide kernels

Worth noting some extra things for anyone else looking at this:

james commented on issue infra/tickets#13279 2026-04-21 20:15:31 +00:00
Signing problem with the latest rawhide kernels

What I know:

james commented on issue infra/tickets#13279 2026-04-21 16:35:12 +00:00
Signing problem with the latest rawhide kernels

Okay, I think this should be working again now.

james commented on issue infra/tickets#13279 2026-04-21 01:03:04 +00:00
Signing problem with the latest rawhide kernels

Okay, I have access to the server logs now and messages is a lot of this repeated:

james commented on issue infra/tickets#13281 2026-04-20 23:24:49 +00:00
Unable to use FAS credentials for BZ login

There is a known FAS login issue where sometimes a 400 error is given, but if you go back to the source immediately the FAS login worked. Is that the problem here?

james commented on issue infra/tickets#13279 2026-04-20 23:06:26 +00:00
Signing problem with the latest rawhide kernels

We are trying to find out who can see the server side logs atm.

james commented on issue infra/tickets#13278 2026-04-20 20:03:31 +00:00
Builds on buildhw-x86-13 stuck with "[Errno 11] Resource temporarily unavailable" errors

It successfully did: https://koji.fedoraproject.org/koji/taskinfo?taskID=144644338 ... so I'm going to close this as "fixed by reboot", please let me know if you see any other weirdness with it…