Bug 1907595 - [sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (ext3)] volumes [Top Level] [sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (ext3)] volumes should store data
Summary: [sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (ext3...
Keywords:
Status: CLOSED DUPLICATE of bug 1785399
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: aos-storage-staff@redhat.com
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-14 19:39 UTC by Jacob Tanenbaum
Modified: 2020-12-15 14:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
[sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (ext3)] volumes [Top Level] [sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (ext3)] volumes should store data
Last Closed: 2020-12-15 14:49:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jacob Tanenbaum 2020-12-14 19:39:19 UTC
test:
[sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (ext3)] volumes [Top Level] [sig-storage] In-tree Volumes [Driver: cinder] [Testpattern: Dynamic PV (ext3)] volumes should store data 

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%28ext3%5C%29%5C%5D+volumes+%5C%5BTop+Level%5C%5D+%5C%5Bsig-storage%5C%5D+In-tree+Volumes+%5C%5BDriver%3A+cinder%5C%5D+%5C%5BTestpattern%3A+Dynamic+PV+%5C%28ext3%5C%29%5C%5D+volumes+should+store+data

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-4.4/1338374880525029376


 Dec 14 07:40:51.250: FAIL: Failed to delete pod "downwardapi-volume-6e0bc494-7a79-4fc9-a73c-b6ff57b18ad1": Delete https://api.70pxntnh-1a357.shiftstack.devcluster.openshift.com:6443/api/v1/namespaces/e2e-projected-5370/pods/downwardapi-volume-6e0bc494-7a79-4fc9-a73c-b6ff57b18ad1: read tcp 172.16.100.120:54894->128.31.26.248:6443: read: connection reset by peer
Full Stack Trace
github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework.(*PodClient).DeleteSyncInNamespace(0xc001aef1e0, 0xc0011ddd80, 0x37, 0xc00199c880, 0x12, 0xc0015a52c0, 0x29e8d60800)
	/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/pods.go:151 +0x39d
github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework.(*PodClient).DeleteSync(...)
Dec 14 07:40:57.571 I ns/openshift-kube-apiserver pod/kube-apiserver-70pxntnh-1a357-flpwh-master-2 Started container kube-apiserver
Dec 14 07:40:57.609 I ns/openshift-kube-apiserver pod/kube-apiserver-70pxntnh-1a357-flpwh-master-2 Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a82623584dc2e4d1ec76380925c976111a55a12a67e457e432cc0e1faf892913" already present on machine
Dec 14 07:40:57.609 I ns/openshift-kube-apiserver pod/kube-apiserver-70pxntnh-1a357-flpwh-master-2 Created container kube-apiserver-cert-syncer
Dec 14 07:40:57.610 I ns/openshift-kube-apiserver pod/kube-apiserver-70pxntnh-1a357-flpwh-master-2 Started container kube-apiserver-cert-syncer
Dec 14 07:40:57.610 I ns/openshift-kube-apiserver pod/kube-apiserver-70pxntnh-1a357-flpwh-master-2 Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a82623584dc2e4d1ec76380925c976111a55a12a67e457e432cc0e1faf892913" already present on machine
Dec 14 07:40:57.610 W ns/openshift-monitoring pod/thanos-querier-7b4bc54cd7-82v4l Readiness probe failed: command timed out

Comment 1 Jan Safranek 2020-12-15 14:49:17 UTC

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


Note You need to log in before you can comment on or make changes to this bug.