Since approx. 1st of December I'm experiencing issues running cbs commands within GitLab CI.
Most of the cbs commands are running into a time out, no connection can be established.
According to the GitLab documentation its runner (for gitlab.com) are deployed into Google Cloud Platform (GCP) in us-east1 1. The IP ranges of GCP can be found here 2.
For reference, mail sent to centos-devel concerning this issue 3.
@arrfab blocked some GCP IPs last week, when there was too many requests to koji, this could be probably the cause of this issue @phsmoura Could you look into this? I don't even know where those IPs are defined
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: cbs, high-gain, low-trouble
@arrfab already confirmed to me yesterday on IRC that the issue is most likely related to blocking some IPs last week due to DoS. However, he also told me that simply allowing back a wide range of IPs is not a solution as it's from where the DoS was coming from.
@pjgeorg Thanks for clarification, but @arrfab is currently off till Friday and I'm not sure how he wants to approach this. Is this urgent or do you want to wait till he is back?
Metadata Update from @zlopez: - Issue untagged with: low-trouble - Issue tagged with: medium-trouble
@zlopez Not urgent. Waiting till he is back is fine for me.
Can you verify ? I temporary removed the restriction from these ranges (and keeping an eye on this)
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)
I can confirm that it is working now.
Thanks for feedback. closing
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.