#8872 Fedora CI not working
Closed: Fixed by kevin. Opened by omos.

Rawhide PR pipelines are consistently failing at the moment:
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/activity

The root cause seems to be:

[...]
[2020-04-29T12:27:31.932Z] + git clone -b master --single-branch https://src.fedoraproject.org/rpms/libkcapi/
[2020-04-29T12:27:31.938Z] Cloning into 'libkcapi'...
[2020-04-29T12:27:46.790Z] fatal: unable to access 'https://src.fedoraproject.org/rpms/libkcapi/': Could not resolve host: src.fedoraproject.org; Unknown error
[...]

@siddharthvipul1 @bstinson could you look at this from the servers there

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

It seems it has started working again around 17:00 UTC. Pipelines are going through now.

siddharthvipul1 commented

@smooge
didn't seem a CI issue from what I could understand.
the message said
fatal: unable to access 'https://src.fedoraproject.org/rpms/libkcapi/': Could not resolve host: src.fedoraproject.org; Unknown error
some network error perhaps?
glad it's back though

It seems that was some temporary outage, I'm not sure if was on Fedora infra or on CentOS one.

Some pipeline jobs also failed to query bodhi:

Could not resolve host: bodhi.fedoraproject.org; Unknown error

like: https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-rawhide-build-pipeline/11657/console

I am pretty sure not on fedora side, as we would have had tons of people complaining about things not resolving, so I suspect it was some local resolver problem on the ci side.

I'll close this now, let us know if you ever see it again...

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

siddharthvipul1 commented

I am pretty sure not on fedora side, as we would have had tons of people complaining about things not resolving, so I suspect it was some local resolver problem on the ci side.
I'll close this now, let us know if you ever see it again...

Hmm, I will take a note of it and see if something pops up again with any other tenants :)
thank you for explaining :)

Metadata