GitLab connection broken after authentication incident this morning

SonarQube Cloud
,
1

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)
    • GitLab
  • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI
    • GitLab

Good afternoon,

We are having issues with our GitLab connection and binding projects to the respective GitLab repositories since about 48h. The issues are showing up in various situations. In our CI we currently encounter mostly the error messages „could not find pull request X“. Looking into SonarCloud it does not show the MR hence the message seems to be correct.

We have deleted some of the project and re-created them via API but are not able to assign/bind them to the respective GitLab repositories. The spinning wheel on Sonar keeps spinning. We have updated the auth token to GitLab and it is reported as valid, but no change in behavior.

This is actively blocking internal development. We would like to get immediate support. We are an Enterprise customer.

Thanks

2

Update: Going to General Settings → Repository binding → GitLab Repository binding the system seems to try to create the available project list but errors out with “An unexpected error occurred. Please try again later.” after about 3-5 min

3

Hey there.

Do you see your organization as correctly bound when you view your org-level Administration > Organization settings > Organization binding?

4

Hi Colin,

I’m working with Matthias on this. The organization binding seems to be fine. It shows our organization names for both SonarQube and GitLab under “current binding”. And also states that the personal access token is valid.

5

Thanks.

If that’s the case, you may want to try binding via the API.

We know that we sometimes face timeouts querying Gitlab when a token has access to a large number of repos. Is that the case here?

6

Yes, I think our use case would qualify as involving a large number of repos. We work for a big company and have more than 1000 users on GitLab, working on various projects.

I’ll contact Matthias and check if he has already tried binding via API. I think he did but I’m not sure.

7

Hi sorry for the late reply. The binding is possible via API, that is not an issue and we have done that consistently. The UI was just an indicator of a bigger problem. We are seeing a lot of projects that are not executing correctly because they don’t find the MRs. This only happens with project that are bound to GitLab projects. Please see the screenshots attached.

image
image637×170 27.5 KB

image
image1168×417 29.3 KB

8

Colin, we think we found the issue at least on the last comment I made. The developer did delete the project in GitLab and re-created it with the exact name and location again. That caused issues with the linking. We had to delete if from sonar and have it re-created, we could not find a way to patch the binding. Do you have any information on how to use the API to re-configure the binding?

9

Hey there.

Wouldn’t that be the same as what I linked earlier?