Deployments for Gitlab continue to fail after reconnect and Render's fix

1

Hello all,

We are once again unable to deploy services from our Gitlab accounts.

The problem seems different in nature to the recent Gitlab related failures which we also experienced. Previously, an internal server error pop-up would appear in Render’s UI when we tried to deploy manually and Render’s advice to reconnect Gitlab fixed this issue.

Now, when deployments fail, the following logs are shown (some text omitted <>):

May 18 11:08:24 AM ==> Cloning from https://gitlab.com/<our-repo-path>...
May 18 11:08:24 AM remote: HTTP Basic: Access denied
May 18 11:08:24 AM fatal: Authentication failed for 'https://oauth2:<some-long-key>e@gitlab.com/<our-repo-path>.git/'
May 18 11:08:24 AM ==> Retrying git clone...
May 18 11:08:31 AM remote: HTTP Basic: Access denied
May 18 11:08:31 AM fatal: Authentication failed for 'https://oauth2:<some-long-key>e@gitlab.com/<our-repo-path>.git/'
May 18 11:08:31 AM ==> Retrying git clone...
May 18 11:08:38 AM remote: HTTP Basic: Access denied
May 18 11:08:38 AM fatal: Authentication failed for 'https://oauth2:<some-long-key>e@gitlab.com/<our-repo-path>.git/'
May 18 11:08:38 AM ==> Retrying git clone...
May 18 11:08:58 AM remote: HTTP Basic: Access denied
May 18 11:08:58 AM fatal: Authentication failed for 'https://oauth2:<some-long-key>e@gitlab.com/<our-repo-path>.git/'
May 18 11:08:58 AM ==> Retrying git clone...
May 18 11:09:23 AM remote: HTTP Basic: Access denied
May 18 11:09:23 AM fatal: Authentication failed for 'https://oauth2:<some-long-key>e@gitlab.com/<our-repo-path>.git/'
May 18 11:09:23 AM ==> Unable to clone https://gitlab.com/<our-repo-path>

So the error is occuring when Render attempts to clone a repository. Render’s connection seems otherwise fine, as all the repositories of the attached Gitlab account are visible within the UI.

Render’s status page states that the Gitlab issues have been resolved, but reconnecting our account has no effects on the current failures. Is anyone else experiencing such failures?

2

We have the same issue here.

3

Hi there.

We’ve seen a handful of reports of subsequent deploy failures following the previous incident. We’ve just pushed a new fix which should address this issue. Are you able to see if things have improved for you? There is a risk if multiple services trigger to deploy at the same time that a race condition can occur and the build would fall - which will definitely be addressed in US working hours, but a ‘Manual Deploy’ click on a service will work.

John B

4

Hi John, thanks for the quick response! We were able to deploy our Web Services, so that looks like it has been fixed.
However, we also have a static site that is pulling from Gitlab, and that one still fails and shows the same log messages as I posted above.

5

Hi John,

Yes, we are able to deploy our web service again. Thank you for your quick response and the fix!

6

@christopher can you jump on a chat via our dashboard please.

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.