Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1812550

Summary: MountVolume.SetUp failed for volume (xyz) causing failures across many pods in CI
Product: OpenShift Container Platform Reporter: bpeterse
Component: NodeAssignee: Ryan Phillips <rphillips>
Status: CLOSED NOTABUG QA Contact: Sunil Choudhary <schoudha>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.zCC: aos-bugs, jokerman
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:
Last Closed: 2020-03-11 16:20:13 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 bpeterse 2020-03-11 15:04:11 UTC 
Description of problem:

This is a CI flake, an example can be seen here:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/19495

A snippet of the logs:

```
 Feb 28 20:18:18.236 W ns/openshift-cluster-samples-operator pod/cluster-samples-operator-5dddd4c77f-tfbhk MountVolume.SetUp failed for volume "samples-operator-tls" : couldn't propagate object cache: timed out waiting for the condition
Feb 28 20:18:18.263 W ns/openshift-cluster-samples-operator pod/cluster-samples-operator-5dddd4c77f-tfbhk MountVolume.SetUp failed for volume "cluster-samples-operator-token-jzlfc" : couldn't propagate object cache: timed out waiting for the condition
Feb 28 20:18:18.289 W ns/openshift-monitoring pod/cluster-monitoring-operator-f596f4f59-hnwzh MountVolume.SetUp failed for volume "cluster-monitoring-operator-token-l96mj" : couldn't propagate object cache: timed out waiting for the condition 
...
 Feb 28 20:18:58.803 W ns/openshift-monitoring pod/prometheus-adapter-84dd595b6f-zrwv5 MountVolume.SetUp failed for volume "config" : couldn't propagate object cache: timed out waiting for the condition
Feb 28 20:18:58.812 W ns/openshift-monitoring pod/prometheus-adapter-84dd595b6f-zrwv5 MountVolume.SetUp failed for volume "prometheus-adapter-token-4gdqr" : couldn't propagate object cache: timed out waiting for the condition
Feb 28 20:18:58.819 W ns/openshift-monitoring pod/prometheus-adapter-84dd595b6f-zrwv5 MountVolume.SetUp failed for volume "tls" : couldn't propagate object cache: timed out waiting for the condition 
...

Feb 28 20:19:28.657 W ns/openshift-apiserver pod/apiserver-qxrbd MountVolume.SetUp failed for volume "image-import-ca" : couldn't propagate object cache: timed out waiting for the condition
Feb 28 20:19:28.658 W ns/openshift-apiserver pod/apiserver-qxrbd MountVolume.SetUp failed for volume "config" : couldn't propagate object cache: timed out waiting for the condition
Feb 28 20:19:28.658 W ns/openshift-apiserver pod/apiserver-qxrbd MountVolume.SetUp failed for volume "trusted-ca-bundle" : couldn't propagate object cache: timed out waiting for the condition
Feb 28 20:19:28.672 W ns/openshift-apiserver pod/apiserver-qxrbd MountVolume.SetUp failed for volume "etcd-client" : couldn't propagate object cache: timed out waiting for the condition 
```


Version-Release number of selected component (if applicable):


How reproducible:

It appears to be a flake, thus causing build failures. 

Additional Info:

Originally reported as part of this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1809259
Comment 1 Ryan Phillips 2020-03-11 16:20:13 UTC 
We have seen this flake before. This is the expected behavior of the object cache... it will become eventually consistent.