#6866 running kojira in stg
Closed: Fixed 5 years ago Opened 6 years ago by dustymabe.

I'm trying to do a pungi compose in stg. One of my lorax runroot tasks is stuck on waitrepo (f26-build). I was told:

18:01:18          mbonnet | dustymabe: the problem is the f26-build tag has no active repo associated with it: https://koji.stg.fedoraproject.org/koji/taginfo?tagID=364 
18:01:50        dustymabe | mbonnet: do you know how to fix that, or know of someone who would know?
18:02:14          mbonnet | dustymabe: kojira is responsible for kicking off repo regens
18:02:24          mbonnet | dustymabe: if it's not running, it would cause this problem
18:02:39          mbonnet | dustymabe: I'd suggest filing a ticket with Fedora rel-eng

Note that I did a manual repo regen last night to move things forward, but kojira in staging needs some work... theres something wrong with permissions and it gets perm denied trying to do things.

Likely this is another bug in the prod->stg sync and needs fixing there and re-running sometime soon.

thanks for the manual sync - do you want to leave this bug opened for the permission issue?

@kevin is this still an issue? What needs done if anything to make sure this keeps working in the future?

We need to make sure and add it to the sync script that syncs from prod->stg

ansible/playbooks/manual/staging-sync/koji

I am not sure if it's in there yet or not. @mizdebsk was working on that script...

TLDR: this should be already fixed

When this issue was reported, kojira was not set up to run in staging, for several reasons. Most importantly, there were a lot of modular build targets and regenerating them would take really long time. We were facing NFS performance problems in production Koji, and running kojira on staging would slow it down even more as NFS netapp is shared between prod and stg. And generating repos for all these modular tags would be pointless anyway. But since modularity started removing unused build targets and switched to external repos, we have much fewer build targets and repos for them can be generated much faster, so kojira is currently enabled in staging and should be running. This can be closed.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata