Learn more about these different git repos.
Other Git URLs
I'm seeing the same repo queued for deletion twice by kojira. E.g.
2021-02-18 02:16:19,284 [INFO] koji.repo.regen: Found repo 4734200, state=READY 2021-02-18 09:12:17,043 [INFO] koji.repo.regen: Repo 4734200 no longer current 2021-02-18 10:06:38,741 [INFO] koji.repo.regen: State changed for repo 4734200: READY -> EXPIRED 2021-02-18 23:08:30,410 [INFO] koji.repo.manager: Found repo 4734200, state=EXPIRED 2021-02-19 15:19:53,127 [INFO] koji.repo.delete: Deleted repo 4734200 2021-02-19 15:19:53,127 [INFO] koji.repo.regen: Queuing rmtree job for /mnt/brew/repos/rhel-8.3.0-build/4734200 2021-02-19 15:19:59,991 [INFO] koji.repo.regen: Started rmtree (pid 581014) for /mnt/brew/repos/rhel-8.3.0-build/4734200 2021-02-19 15:20:15,011 [INFO] koji.repo.regen: pid 581014 (/mnt/brew/repos/rhel-8.3.0-build/4734200) exited with status 0 2021-02-19 15:20:15,014 [INFO] koji.repo.regen: Completed rmtree job for /mnt/brew/repos/rhel-8.3.0-build/4734200 2021-02-19 15:21:13,059 [INFO] koji.repo.regen: Found repo 4734200, state=EXPIRED 2021-02-19 15:21:24,426 [INFO] koji.repo.delete: Repo directory does not exist: /mnt/brew/repos/rhel-8.3.0-build/4734200 2021-02-19 15:21:24,452 [INFO] koji.repo.delete: Deleted repo 4734200 2021-02-19 15:21:24,453 [INFO] koji.repo.regen: Queuing rmtree job for /mnt/brew/repos/rhel-8.3.0-build/4734200 2021-02-19 15:21:30,451 [INFO] koji.repo.regen: Started rmtree (pid 581062) for /mnt/brew/repos/rhel-8.3.0-build/4734200 2021-02-19 15:21:30,459 [WARNING] koji: No such file/dir /mnt/brew/repos/rhel-8.3.0-build/4734200 for removal 2021-02-19 15:21:45,486 [INFO] koji.repo.regen: pid 581062 (/mnt/brew/repos/rhel-8.3.0-build/4734200) exited with status 0 2021-02-19 15:21:45,487 [INFO] koji.repo.regen: Completed rmtree job for /mnt/brew/repos/rhel-8.3.0-build/4734200
While this should in principle be harmless, it could be slowing down the delete queue and it could exacerbate #2714
Metadata Update from @mikem: - Custom field Size adjusted to None
PR #2755
Metadata Update from @tkopecek: - Issue tagged with: testing-ready
Metadata Update from @tkopecek: - Issue set to the milestone: 1.24.1
Metadata Update from @tkopecek: - Issue untagged with: testing-ready - Issue tagged with: no_qe
Commit 788b277 fixes this issue
Commit e83dd27 fixes this issue
Login to comment on this ticket.