-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
False
-
None
-
False
-
-
storage related issues on https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-gcp-ovn-upgrade-4.17-micro-release-openshift-release-analysis-aggregator/1793540090580963328
: [sig-storage] PersistentVolumes GCEPD [Feature:StorageProvider] should test that deleting the PV before the pod does not cause pod deletion to fail on PD detach [Skipped:NoOptionalCapabilities] [Suite:openshift/conformance/parallel] [Suite:k8s] expand_less
Run #0: Failed expand_less 6s
{ fail [k8s.io/kubernetes@v1.29.0/test/e2e/storage/persistent_volumes-gce.go:53]: PV Create API error: persistentvolumes "gce-" is forbidden: error querying GCE PD volume e2e-810ec81a-0be2-495d-b9f5-38210658de99: disk is not found
Ginkgo exit error 1: exit with code 1}
: [sig-storage] PersistentVolumes GCEPD [Feature:StorageProvider] should test that deleting the PV before the pod does not cause pod deletion to fail on PD detach [Skipped:NoOptionalCapabilities] [Suite:openshift/conformance/parallel] [Suite:k8s] expand_less Run #0: Failed expand_less 6s { fail [k8s.io/kubernetes@v1.29.0/test/e2e/storage/persistent_volumes-gce.go:53]: PV Create API error: persistentvolumes "gce-" is forbidden: error querying GCE PD volume e2e-810ec81a-0be2-495d-b9f5-38210658de99: disk is not found Ginkgo exit error 1: exit with code 1} stdout: [sig-storage] PersistentVolumes GCEPD [Feature:StorageProvider] should test that deleting the PV before the pod does not cause pod deletion to fail on PD detach [Skipped:NoOptionalCapabilities] [Suite:openshift/conformance/parallel] [Suite:k8s] [sig-storage, Feature:StorageProvider] k8s.io/kubernetes@v1.29.0/test/e2e/storage/persistent_volumes-gce.go:148 STEP: Creating a kubernetes client @ 05/23/24 09:10:08.289 STEP: Building a namespace api object, basename pv @ 05/23/24 09:10:08.29 May 23 09:10:08.391: INFO: About to run a Kube e2e test, ensuring namespace/e2e-pv-3161 is privileged STEP: Waiting for a default service account to be provisioned in namespace @ 05/23/24 09:10:08.629 STEP: Waiting for kube-root-ca.crt to be provisioned in namespace @ 05/23/24 09:10:08.686 STEP: Initializing Test Spec @ 05/23/24 09:10:08.743 W0523 09:10:08.746797 30844 gce_instances.go:411] Cloud object does not have informers set, should only happen in E2E binary. May 23 09:10:11.178: INFO: Successfully created a new PD in zone "": "e2e-810ec81a-0be2-495d-b9f5-38210658de99". STEP: Creating the PV and PVC @ 05/23/24 09:10:11.178 May 23 09:10:11.178: INFO: Creating a PV followed by a PVC May 23 09:10:11.446: INFO: Unexpected error: <*fmt.wrapError | 0xc0052ec440>: PV Create API error: persistentvolumes "gce-" is forbidden: error querying GCE PD volume e2e-810ec81a-0be2-495d-b9f5-38210658de99: disk is not found { msg: "PV Create API error: persistentvolumes \"gce-\" is forbidden: error querying GCE PD volume e2e-810ec81a-0be2-495d-b9f5-38210658de99: disk is not found", err: <*errors.StatusError | 0xc0019b9360>{
In sippy, we pick test matching "[sig-storage] PersistentVolumes GCEPD", on gcp, amd64, and micro upgrade to see the failures
- links to