Remote repository couldn't be reached in GCP

Google Cloud Data Analytics
1

Hi there,

Hi there,
Hope someone will be able to help me. I built simple pipleline in Dataform repo (connected to GitHub repo) and execute via Workflows in GCP and this morning around 2.37am it is failed. I had the same issue before and happens again. This is the error message i see in Workflows execution logs:

"HTTP server responded with error code 400
in step "unhandled_exception", routine "main", line: 28: {"body":{"error":{"code":400,"message":"Remote repository 'https://github.com/xxxx/xxxx.git' could not be reached.","status":"INVALID_ARGUMENT"}}

checked trouble shooting in Google Dataform docs: https://cloud.google.com/dataform/docs/troubleshooting#remote_github_repository_cannot_be_reached_ge…

sysph_0-1692259787832.png
sysph_0-1692259787832.png400Ă—148 29.1 KB

So it could be dropped GitHub or GitLab connection. It said There is no need to take any action. Unless GitHub or GitLab issues persist, the subsequent scheduled releases can be successful.

Any thoughts? Thanks

1 Like
2

Based on the error message and the troubleshooting guide you provided, it appears that the connection to GitHub might have been temporarily disrupted. This could be due to various reasons such as a network outage, issues with GitHub servers, or firewall restrictions.

Immediate Recommendations:

  1. GitHub Server Status: Check the current status of GitHub servers at GitHub Status Page to see if there are any ongoing issues.
  2. Firewall Settings: Ensure your firewall settings permit traffic to and from GitHub servers.
  3. Re-authenticate: Consider re-authenticating your connection with GitHub in Dataform to refresh the connection.

Additional Troubleshooting Steps:

  1. Repository URL: Double-check that the GitHub repository URL configured in your Dataform project is correct.
  2. Local Execution: Try executing the Dataform workflow locally. If the issue is reproducible, it might provide more insights.
  3. Proxy Server: If you’re utilizing a proxy server, ensure it’s correctly configured to allow access to GitHub.
2 Likes
3

Thanks so much again, @ms it’s so helpful.

I will do the checks.

After i manually executing Workflows, it ran successfully.

1 Like
4

Hello good day, I am facing somewhat a similar problem to this and I was excited to try your suggestions since it worked for @sysph . But, I just realized that it was for a GitHub and not GitLab. I was wondering if you could help me with this error in release configuration in Dataform which causes tables in Mongodb-prod to not update daily.

Error says:

annebaby99_0-1710840017689.png

It would be nice to hear from you soon, thanks!

5

Hi @annebaby99 ,

sorry for late replying. yes, it is for GitHub i was using. We decided not to connect to github for the time being

Based on your error message in the trouble shooting doc here https://cloud.google.com/dataform/docs/troubleshooting#remote-repository-invalid

No need to take any action.

1 Like
6

The error message you’re encountering suggests that the connection to your GitLab repository was closed unexpectedly during a remote operation. This could be due to a variety of reasons, including network issues, GitLab server problems, or configuration errors in your Dataform setup. Let’s adapt the troubleshooting approach for GitLab:

  1. Check GitLab Status

First, verify the operational status of GitLab by checking the GitLab status page. Any ongoing incidents or recent outages could explain the connectivity issues you’re experiencing.

  1. Validate the Repository URL

Ensure that the URL for your GitLab repository is correct in your Dataform configuration. The error message includes the repository URL, so you can compare it directly to ensure there are no typos or mistakes. Also, ensure that the repository is still accessible and hasn’t been moved or deleted.

  1. Network and Firewall Settings

Similar to GitHub, network configurations or firewall settings could block traffic to and from GitLab. Ensure that your network allows connections to GitLab, and consider any corporate proxies or VPNs that might affect connectivity.

  1. Authentication and Permissions

If your Dataform project requires authentication to access the GitLab repository (which is likely for private repositories), ensure that your credentials are up to date. For GitLab, this could involve personal access tokens or deploy keys. Verify that the token or key has the necessary permissions and hasn’t expired or been revoked.

  1. Retry Strategy

Given that network issues can be transient, implementing a retry strategy in your Dataform project or workflow can help mitigate temporary connectivity problems. If possible, configure retries with exponential backoff to reduce the likelihood of repeated failures during short-lived network issues.

  1. Local Execution Test

Try executing your Dataform project locally or in a different environment to see if the issue persists. This can help determine whether the problem is specific to the environment where your Dataform project runs.

  1. Examine GitLab API Rate Limits

Although the error message doesn’t specifically mention rate limiting, it’s worth considering, especially if your Dataform project makes frequent requests to GitLab. Check the GitLab documentation on rate limits to ensure you’re not exceeding them.

  1. Contact Support

If you’re unable to resolve the issue and it significantly impacts your workflow, consider reaching out to GitLab support for assistance. They may provide insights specific to your repository or account.

  1. Monitor and Log

Use logging and monitoring tools to gather more information about the failure. Detailed logs can offer clues that help diagnose connectivity issues more effectively.

While the troubleshooting steps for GitLab are similar to those for GitHub, focusing on GitLab-specific resources and settings (such as the GitLab status page and API rate limits) can help address the issue more directly. By methodically working through these steps, you should be able to identify and resolve the connectivity issue affecting your Dataform project and MongoDB production updates.

1 Like