containerd package has the same tarball checksum problems as others

[afbjorklund]

Building the ISO fails, since the upstream git archive randomly changes checksum.

This is due to including vendor/k8s.io/client-go/pkg/version/.gitattributes

base.go export-subst

The substitution will corrupt the git archive, by filling the git info with wrong information.

58,59c58,59
< 	gitVersion   string = "v0.0.0-master+$Format:%h$"
< 	gitCommit    string = "$Format:%H$" // sha1 from git, output of $(git rev-parse HEAD)
---
> 	gitVersion   string = "v0.0.0-master+1e5ef943eb"
> 	gitCommit    string = "1e5ef943eb76627a6d3b6de8cd1ef6537f393a71" // sha1 from git, output of $(git rev-parse HEAD)

It was intended to record the kubernetes version, but here has a random short rev of containerd.

Problems started with containerd 1.5.x, that started including k8s.io/client-go (unlike 1.4.x)

[afbjorklund]

Broke the ISO build in PR #13089

[afbjorklund]

Reported as:

• including git attributes in "vendor" makes archive checksum change containerd/containerd#6387

[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

[sharifelgamal]

Yeah, we've seen this happen on occasion for containerd and crio, not a whole lot we can do about it except fix the hash for the time being.

[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

[afbjorklund]

Fixed in containerd 1.6