Identify / Fix causes of corruption in .git directory

[akhilerm]

There are cases of corruption in .git directory that occurs randomly while running the publishing-bot which causes the bot to fail. Sometimes a PVC cleanup and restart fixes the issue.

This will be an umbrella issue to track such corruptions and identify possible solutions:

A few of the recurring corruption issues are listed below

• fatal: unexpected line in .git/packed-refs Ref: kubernetes publishing bot is broken kubernetes#56876 (comment)
• error in checking out a commit Ref: kubernetes publishing bot is broken kubernetes#56876 (comment)

The above 2 issues get fixed after cleaning up of the PVC

• reference has changed concurrently Ref: kubernetes publishing bot is broken kubernetes#56876 (comment). This sometimes get fixed during a rerun. This issue has been reported in go-git which publishing-bot uses for some git operations.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[akhilerm]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[akhilerm]

/remove-lifecycle stale

[akhilerm]

For the reference has changed concurrently issue, a patch has been merged in go-git. go-git/go-git#1116. Will pick it up in next release and see if it fixes our issue.

[pjbgf]

@akhilerm it is uncertain when a next release of go-git will be cut, the current recommendation is for users to use a pseudo version out of master instead.

[akhilerm]

Thanks for the update @pjbgf . Will go through the rest of the changes that went into master after v5.12.0 which we currently use and then see if we can update to a commit.