Remote builds randomly timeout: hit 27s timeout running '/usr/bin/git fetch --depth=1 origin master'

[VackarAfzal]

When running a build on an overlay containing multiple remote components, I randomly get timeouts

Expected output

Should build the overlay as expected

Actual output

Sometimes builds, but sometimes fails with this error message

Error: accumulating resources: accumulation err='accumulating resources from 'git@***************?ref=master': evalsymlink failure on '*********************** 
no such file or directory': hit 27s timeout running '/usr/bin/git fetch --depth=1 origin master'

Kustomize version

{Version:kustomize/v4.0.5 GitCommit:9e8e7a7fe99ec9fbf801463e8607928322fc5245 BuildDate:2021-03-08T20:53:03Z GoOs:darwin GoArch:amd64}

Platform

Linux/macOS

Additional context

I upgraded from 2.x to 4.x then saw this behaviour appear

[mxrss2]

https://github.com/kubernetes-sigs/kustomize/blob/017a0944383d28378ae7a2f063a630b6c124b16c/api/internal/git/gitrunner.go

@VackarAfzal this is the code that does this -- may be an opportunity to add in a PR to override this cause its suboptimal to not be able to override it.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[daxmc99]

Adding ?timeout=90s to the query parameters can now fix this per https://github.com/kubernetes-sigs/kustomize/blob/master/examples/remoteBuild.md

[Zia-Eurus]

@daxmc99 how to specify this timeout variable. can you please give a sample example?

[jasonicarter]

@daxmc99 how to specify this timeout variable. can you please give a sample example?

This is an Airbyte example, where the timeout=90s is appended at the end (works for me)

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
  - https://github.com/airbytehq/airbyte.git/kube/overlays/stable?ref=master&timeout=90s