kubernetes: Will download and extract kubernetes-test tarball(s) - curl: (22) The requested URL returned error: 403

Many jobs are failing because of

 I0220 10:10:17.124] Will download and extract kubernetes-test tarball(s) from https://storage.googleapis.com/kubernetes-release-dev/ci/v1.19.0-alpha.0.64+937008e3aca75c
I0220 10:10:17.124] https://www.googleapis.com/auth/cloud-platform
W0220 10:10:17.225]   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
W0220 10:10:17.225]                                  Dload  Upload   Total   Spent    Left  Speed
W0220 10:10:17.328] 
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
W0220 10:10:17.328] curl: (22) The requested URL returned error: 403 

Some of the job logs: https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-ingress/1230434368032346114 https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-ingress/1230434368032346114 https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-scalability/1230440661795213312#1:build-log.txt%3A205 https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-gce-conformance-latest/1230420526376161281#1:build-log.txt%3A161

/priority critical-urgent /cc @kubernetes/ci-signal /cc @justaugustus @alejandrox1 @kubernetes/release-managers /milestone v1.18

/sig release

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 23 (23 by maintainers)

Most upvoted comments

@spiffxp filed a number of cherry picks for the script

Also, all the jobs report in their log the following:

bootstrap.py is deprecated!
test-infra oncall does not support any job still using bootstrap.py.
Please migrate your job to podutils!
https://github.com/kubernetes/test-infra/blob/master/prow/pod-utilities.md

@justaugustus Do we have to take any action to change that?

Switching from bootstrap.py to podutils should be done by the job owners - this is out of scope for releas team (strictly speaking). And the message is just a warning, should not affect the job itself.