I built systemd-247.3-2.hs.el8 and systemd-247.3-2.hs+fb.el8 today around noon PST, and tagged them for -testing (hyperscale8s-packages-main-testing and hyperscale8s-packages-facebook-testing respectively), but I've noticed the packages still haven't appeared under https://buildlogs.centos.org/centos/8-stream/hyperscale/x86_64
systemd-247.3-2.hs.el8
systemd-247.3-2.hs+fb.el8
-testing
hyperscale8s-packages-main-testing
hyperscale8s-packages-facebook-testing
Is something wrong, or do we just need to wait? What's the expected SLA between tagging and publishing? Thanks!
In case it helps, here's what I found in my terminal history:
$ cbs tag-build hyperscale8s-packages-main-testing systemd-247.3-2.hs.el8 Created task 1983920 Watching tasks (this may be safely interrupted)... 1983920 tagBuild (noarch): free 1983920 tagBuild (noarch): free -> closed 0 free 0 open 1 done 0 failed 1983920 tagBuild (noarch) completed successfully $ cbs tag-build hyperscale8s-packages-facebook-testing systemd-247.3-2.hs+fb.el8 Created task 1983921 Watching tasks (this may be safely interrupted)... 1983921 tagBuild (noarch): free 1983921 tagBuild (noarch): free -> closed 0 free 0 open 1 done 0 failed 1983921 tagBuild (noarch) completed successfully $
Hi @dcavalca
while still on PTO, I just had a quick look Current signing queue stats :
Current number of job[s] in queue in [signing]: 697 Sat 20 Feb 09:10:59 UTC 2021
So that means that another SIG tag plenty of pkgs but instead of tagging all in one shot, they just tagged one by one and with some intervals, just filing the queue : if you look at cbs.centos.org (now) you'll see plenty of tagged pkg by RDO for openstack-train-{testing,release} I've already reached out to @amoralej to see how they can do that in a more efficient way but at this stage it will just be better to let the queue being processed and pkgs will land automatically after on buildlogs
Ah, thanks! I hadn't realized there was a queue, but this totally makes sense. There's no rush right now, we can wait for the queue to clear.
I see that now queue was fully processed :
Current number of job[s] in queue in [signing]: 0 Sat 20 Feb 11:01:50 UTC 2021
and pkgs landed on buildlogs : https://buildlogs.centos.org/centos/8-stream/hyperscale/x86_64/packages-main/Packages/s/systemd-247.3-2.hs.el8.x86_64.rpm (one example)
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Metadata Update from @arrfab: - Issue assigned to arrfab - Issue tagged with: Business-As-Usual, cbs, low-gain, low-trouble
Hi @dcavalca while still on PTO, I just had a quick look Current signing queue stats : Current number of job[s] in queue in [signing]: 697 Sat 20 Feb 09:10:59 UTC 2021 So that means that another SIG tag plenty of pkgs but instead of tagging all in one shot, they just tagged one by one and with some intervals, just filing the queue : if you look at cbs.centos.org (now) you'll see plenty of tagged pkg by RDO for openstack-train-{testing,release} I've already reached out to @amoralej to see how they can do that in a more efficient way but at this stage it will just be better to let the queue being processed and pkgs will land automatically after on buildlogs
while still on PTO, I just had a quick look Current signing queue stats : Current number of job[s] in queue in [signing]: 697 Sat 20 Feb 09:10:59 UTC 2021
We implemented some changes in our tooling to do massive tagging in one shot but apparently it didn't work as expected this time, I'll check what happened in this case.
Login to comment on this ticket.