Bug 1927709

Summary:	[sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Product:	OpenShift Container Platform	Reporter:	Stefan Schimanski <sttts>
Component:	Storage	Assignee:	aos-storage-staff <aos-storage-staff>
Storage sub component:	Storage	QA Contact:	Qin Ping <piqin>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	aos-bugs, jsafrane
Version:	4.7
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	[sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents
Last Closed:	2021-02-11 14:38:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stefan Schimanski 2021-02-11 11:28:39 UTC

test:
[sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (default fs)] fsgroupchangepolicy (OnRootMismatch)[LinuxOnly], pod created with an initial fsgroup, new pod fsgroup applied to volume contents 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-storage%5C%5D+In-tree+Volumes+%5C%5BDriver%3A+cinder%5C%5D+%5C%5BTestpattern%3A+Dynamic+PV+%5C%28default+fs%5C%29%5C%5D+fsgroupchangepolicy+%5C%28OnRootMismatch%5C%29%5C%5BLinuxOnly%5C%5D%2C+pod+created+with+an+initial+fsgroup%2C+new+pod+fsgroup+applied+to+volume+contents


FIXME: Replace this paragraph with a particular job URI from the search results to ground discussion.  A given test may fail for several reasons, and this bug should be scoped to one of those reasons.  Ideally you'd pick a job showing the most-common reason, but since that's hard to determine, you may also chose to pick a job at random.  Release-gating jobs (release-openshift-...) should be preferred over presubmits (pull-ci-...) because they are closer to the released product and less likely to have in-flight code changes that complicate analysis.

FIXME: Provide a snippet of the test failure or error from the job log

Comment 1 Jan Safranek 2021-02-11 14:38:07 UTC

The test is skipped on all platforms except for OpenStack. Since literally none of the failures in the linked search are from OpenStack, it must be a transient error in BeforeEach / AfterEach, where a namespace is created and the tests wait for all nodes to be Running and whatnot.

Quick scan of the logs shows:

E0208 19:49:49.809080   35167 test_context.go:485] 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

Get "https://api.ci-op-bi6jsh54-3caf3.origin-ci-int-gce.dev.openshift.com:6443/api/v1/nodes?fieldSelector=spec.unschedulable%3Dfalse&resourceVersion=0": dial tcp 34.75.5.158:6443: i/o timeout occurred

Get "https://api.ci-op-iz7mfw28-164ae.origin-ci-int-aws.dev.rhcloud.com:6443/api/v1/nodes?fieldSelector=spec.unschedulable%3Dfalse&resourceVersion=0": x509: certificate signed by unknown authority

error: Get "https://api.libvirt-ppc64le-1-0-b5318.libvirt-ppc64le-1-0:6443/apis/config.openshift.io/v1/infrastructures/cluster": dial tcp 172.30.254.137:6443: connect: connection refused

error: Get "https://api.libvirt-s390x-0-2-ce101.libvirt-s390x-0-2:6443/apis/config.openshift.io/v1/infrastructures/cluster": net/http: TLS handshake timeout

error: an error on the server ("") has prevented the request from succeeding (get infrastructures.config.openshift.io cluster)

fail [runtime/panic.go:969]: Test Panicked: runtime error: invalid memory address or nil pointer dereference

*** This bug has been marked as a duplicate of bug 1890131 ***