The web interface returns:
504 Gateway Time-out The server didn't respond in time.
According to prometheus the CI jobs are not running and they are stuck on queue.
Metadata Update from @pingou: - Issue assigned to siddharthvipul1 - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: ci
The UI sometimes loads and there are dozens of builds running, except they all (at least those that I checked) are stuck at the very beginning:
Triggered by CI message. Checking out git https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline into /var/lib/jenkins/jobs/fedora-task-pipeline-trigger/workspace@script to read JenkinsfileTaskTrigger
New Fedora CI generic checks were stuck on sending CI messages. So it seems like some kind of a network issue (?)
Jenkins master POD was redeployed, I'm not sure if someone did it or it happened automatically.
I see some jobs running, but very slow, like https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-build-pipeline-trigger/454308/console these trigger builds should take usually just few seconds....
It was done from our side
I see some jobs running, but very slow, like https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-build-pipeline-trigger/454308/console these trigger builds should take usually just a few seconds....
It will take a little bit of time to clear the queue and hopefully things will be back to normal
I will monitor as my teammates in Brno are logging out for the day :)
Metadata Update from @siddharthvipul1: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.