As we keep increasing QA activities, we are noticing that, downloading RC images from [https://kojipkgs.fedoraproject.org/compose/38/latest-Fedora-38/compose/Workstation/x86_64/iso/] is very slow. In the last few releases, we have RCs that drop one or two days before the Go/No-Go. In most of the cases, we have a parallel test day/week running as well. Being an RHT employee it becomes hard enough to wait for RC to download one image, let alone multiple (more if I have to download test day artifacts). I am only wondering, just how much a community member would get affected. I corresponded with @kparal , just to check if this is my internet and he seems to have the same problem in Brno.
Actionable, would be to rsync RCs right after they are created in alt/stage of the dl.fp.o (somewhat automated will help)
ASAP
To make this request clearer, we'd really like to see if https://dl.fedoraproject.org/pub/alt/stage/ was populated automatically after an RC is built. Currently it's a manual task that has a considerable delay. Koji download speeds are very slow sometimes (and especially in Asia, where Sumantro is) and we can't easy automate syncing. Whereas the stage/ dir can easily easily rsynced.
stage/
This means both manual and automated testing has a long delay in some parts of the world, making it very hard to perform QA tasks shortly before the release, when timing is essential.
Please populate the stage/ dir automatically, thank you.
This is more releng than infra thing.
By RC you mean nightly composes of the branched release? Because those are not RC from the Fedora point of view. Release Candidates are made manually and synced after done to the mirror.
No, we don't mean nightly, we really mean Release Candidates (those composes which are already present in stage/, just not synced there automatically).
@sumantrom Can you re-file this under https://pagure.io/releng/ and put a link here? Thanks.
Sumantro created it here: https://pagure.io/releng/issue/11358
I think we can close this.
Sumantro created it here: https://pagure.io/releng/issue/11358 I think we can close this. Sumantro created it here: https://pagure.io/releng/issue/11358 I think we can close this.
yep
Metadata Update from @sumantrom: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.