koji

#4236 wait-repo waits forever for existing repo
Closed: Dropped by mikem. Opened by djdelorie.

Closed: Dropped
Reopen Issue

wrt: https://osci-jenkins-1.ci.fedoraproject.org/job/scratch-build-test/1543/execution/node/35/log/
for https://bodhi.fedoraproject.org/updates/FEDORA-2024-21c649303b
using https://github.com/fedora-ci/scratch-build-test

It looks like "koji wait-repo" is waiting forever (then timing out) for a repo that already exists and has the requrested build in it:

dj@rawhide pts/1 ~/fedsrc/glibc
$ koji list-tagged f42-build-side-98414
Build Tag Built by

glibc-2.40.9000-7.fc42 f42-build-side-98414 djdelorie

dj@rawhide pts/1 ~/fedsrc/glibc
$ koji wait-repo -v --build glibc-2.40.9000-7.fc42 f42-build-side-98414
The --request option is recommended for faster results
This tag is not configured for automatic regeneration
Waiting on repo for f42-build-side-98414
Got repo without needed builds
Waiting for nvrs ['glibc-2.40.9000-7.fc42'] in tag f42-build-side-98414
Waiting for nvrs ['glibc-2.40.9000-7.fc42'] in tag f42-build-side-98414
Waiting for nvrs ['glibc-2.40.9000-7.fc42'] in tag f42-build-side-98414

dj@rawhide pts/1 ~/fedsrc/glibc
$ rpm -q koji
koji-1.35.0-1.fc42.noarch

repo regeneration is on-demand in 1.35. Use the --request option as the command suggests

Metadata Update from @mikem:
- Custom field Size adjusted to None

Let me explain a bit more.

The wait-repo command was always passively waited for new repo. With the new on-demand system that might never happen (hence the suggestion of adding --request and the warning about lack of auto regen). Otoh, passive waiting might still be valid and desired, e.g. if the tag is configured for auto regen, or is otherwise used enough that a build or other action would trigger one. We opted not to change the default behavior and add the --request option (this requires auth, while the default case does not) that will request a regen.

In your case, the current (and so far only) repo for f42-build-side-98414 is 6525017, which contains glibc-2.40.9000-6.fc42, not 7.fc42. This repo was generated before the later glibc build was tagged. So, while there is already a repo, it does not have the requested build.

With the --request option I get

$ time koji wait-repo -v --build glibc-2.40.9000-7.fc42 f42-build-side-98414 --request
Waiting on repo for f42-build-side-98414
Got repo without needed builds
Waiting for nvrs ['glibc-2.40.9000-7.fc42'] in tag f42-build-side-98414
Requesting a repo
Got request: 1098
Request updated: task_id: None -> 124862274
Request updated: task_state: None -> FREE
Request updated: tries: 0 -> 1
Request updated: task_state: FREE -> ASSIGNED
Request updated: task_state: ASSIGNED -> OPEN
Got repo 6525198
Repo info: http://localhost/koji/repoinfo?repoID=6525198
real    3m59.791s
user    0m0.656s
sys 0m0.058s

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

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/4236

Please continue any further discussion there.
Metadata
None
None
None
None
Low
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.