Failure cluster [7c6a1a37...] kops-ci/markers/release-1.29/latest-ci-updown-green.txt returned 404
Closed this issue · 8 comments
Failure cluster 7c6a1a378bc46e2cd5e1
Error text:
init failed to download kops from url: https://storage.googleapis.com/kops-ci/markers/release-1.29/latest-ci-updown-green.txt returned 404
Recent failures:
4/1/2024, 7:39:17 AM e2e-kops-grid-cilium-etcd-al2023-k28-ko29
4/1/2024, 7:13:58 AM e2e-kops-grid-calico-u2004-k26-ko29
4/1/2024, 6:26:44 AM e2e-kops-grid-flannel-u2204-k25-ko29
4/1/2024, 6:25:17 AM e2e-kops-grid-cilium-u2004-k29-ko29
4/1/2024, 6:21:17 AM e2e-kops-grid-kubenet-u2204-k29-ko29
/kind failing-test
/transfer kops
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
/sig <group-name>/wg <group-name>/committee <group-name>
Please see the group list for a listing of the SIGs, working groups, and committees available.
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.
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
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.
/triage accepted
@upodroid @ameukam Any thoughts on this?
https://testgrid.k8s.io/kops-versions#kops-pipeline-updown-kops129
I0401 14:14:44.304366 13778 publish.go:62] gsutil -h Cache-Control:private, max-age=0, no-transform cp /tmp/kops-version-marker4252453504 gs://kops-ci/markers/release-1.29/latest-ci-updown-green.txt
Copying file:///tmp/kops-version-marker4252453504 [Content-Type=application/octet-stream]...
/ [0 files][ 0.0 B/ 105.0 B]
AccessDeniedException: 403 prow-build@k8s-infra-prow-build.iam.gserviceaccount.com does not have storage.objects.create access to the Google Cloud Storage object. Permission 'storage.objects.create' denied on resource (or it may not exist).
The prowjob is currently on the wrong build cluster. Should be cluster: default.
Currently traveling this week, I'll work on setup a new bucket when I'm back.
@hakman: Closing this issue.
In response to this:
Back to green, thanks @ameukam & @dims!
% curl https://storage.googleapis.com/kops-ci/markers/release-1.29/latest-ci-updown-green.txt https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.29.0-beta.2+v1.29.0-beta.1-9-gad346e9bfe/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.