test: [sig-storage] GCP Volumes GlusterFS [Top Level] [sig-storage] GCP Volumes GlusterFS should be mountable [Suite:openshift/conformance/parallel] [Suite:k8s] failed, see job: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-shared-vpc-4.4/96 GCP-related Test running on AWS?
Running "GCP Volumes GlusterFS" on AWS is fine, it tests GlusterFS volumes that are available everywhere. Question is why the test fails: fail [k8s.io/kubernetes/test/e2e/common/volumes.go:132]: defer: Gluster delete endpoints failed Unexpected error: <*errors.StatusError | 0xc001aa8460>: { ErrStatus: { TypeMeta: {Kind: "", APIVersion: ""}, ListMeta: { SelfLink: "", ResourceVersion: "", Continue: "", RemainingItemCount: nil, }, Status: "Failure", Message: "endpoints \"gluster-server\" not found", Reason: "NotFound", Details: { Name: "gluster-server", Group: "", Kind: "endpoints", UID: "", Causes: nil, RetryAfterSeconds: 0, }, Code: 404, }, } endpoints "gluster-server" not found occurred
Adding search results: https://search-clayton-ci-search.apps.build01.ci.devcluster.openshift.com/?search=will+orphan+all+RCs+and+adopt+them+back+when+recreated&maxAge=336h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job Sippy analysis says this fails about 1.5% of the time in 4.5.
Upstream PR: https://github.com/kubernetes/kubernetes/pull/90715
The last error is in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.5/1057, in this e2e test the patch was not merged yet. After this job, this issue is not found yet. But for this issue does not happen always, and it's ratio is 1.5% in OCP4.5, so I'll watch more time to verify this bug.
Checked the ci jobs from 1058~1120, no this issue found. So, marked this bug as verified.
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409