install_kustomize.sh occasionally fails

[EdwardCooke]

What happened?

We're running into an issue where periodically the install_kustomize.sh script doesn't work. Upon debugging, the release_url gets set to this https://api.github.com/repos/kubernetes-sigs/kustomize/releases/284452445 which is the url of the release file itself

Doesn't happen all the time, and in fact usually it does work. I'm working on getting the release json file when it doesn't.

The error from the install.sh is

#11 ERROR: process "/bin/sh -c curl -s \"https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh\" | bash     && mv kustomize /usr/local/bin/kustomize     && chmod +x /usr/local/bin/kustomize" did not complete successfully: exit code: 2
------
 > [ 6/13] RUN curl -s "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh" | bash     && mv kustomize /usr/local/bin/kustomize     && chmod +x /usr/local/bin/kustomize:
1.050 tar (child): ./kustomize_v*_linux_amd64.tar.gz: Cannot open: No such file or directory
1.050 tar (child): Error is not recoverable: exiting now
1.050 tar: Child returned status 2
1.050 tar: Error is not recoverable: exiting now

What did you expect to happen?

install_kustomize.sh always works.

How can we reproduce it (as minimally and precisely as possible)?

Execute curl -s "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh" | bash.

Expected output

It downloads the kustomize executable

Actual output

The error stating the tar file cannot be found

Kustomize version

All

Operating system

Linux

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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-sigs/prow repository.

[EdwardCooke]

Attached is the release json as downloaded. Most of the time it is pretty formatted, the broken time is showing it as a single line.

releases.json

[koba1t]

same issue of #4769

/triage accepted