[sig-storage] Pod Disks should be able to delete a non-existent PD without error
is failing frequently in CI, see search results:
Nikolas, please file these against the components with the failing test rather than the job that had the failure.
This contains only "Failed to setup provider config for "gce": Error building GCE/GKE provider: unexpected response listing zones: googleapi: Error 403: Quota exceeded for quota group 'ListGroup' and limit 'List requests per 100 seconds' of service 'compute.googleapis.com' for consumer 'project_number:1053217076791'., rateLimitExceeded".
I checked the other issues in linked search, it's the usual set of "rateLimitExceeded", "connection refused", "watch closed before UntilWithoutRetry timeout", "i/o timeout" and so on that we track in bug #1890131.
What's new here is:
fail [k8s.io/kubernetes/test/e2e/storage/pd.go:84]: Requires at least 2 nodes
to be >=
The test should be skipped on 2 node cluster.
Posted PR upstream: https://github.com/kubernetes/kubernetes/compare/master...jsafrane:skip-2node?expand=1
Could you please help submit a PR to origin repo? Thanks!
Thanks for heads-up, I created https://github.com/openshift/origin/pull/25852
Verified with the following test log:
skip [k8s.io/kubernetes.0/test/e2e/storage/pd.go:76]: Requires at least 2 nodes (not 0)
skipped: (1.7s) 2021-01-31T21:02:55 "[sig-storage] Pod Disks should be able to delete a non-existent PD without error [Suite:openshift/conformance/parallel] [Suite:k8s]"
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.