Bug 1862196 - After upgrading to 4.4.13 seeing mounts time out across the cluster
Summary: After upgrading to 4.4.13 seeing mounts time out across the cluster
Keywords:
Status: CLOSED DUPLICATE of bug 1836198
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: ceph
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Scott Ostapovicz
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-30 17:17 UTC by emahoney
Modified: 2023-10-06 21:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-30 18:09:13 UTC
Embargoed:


Attachments (Terms of Use)

Description emahoney 2020-07-30 17:17:52 UTC
Description of problem (please be detailed as possible and provide log
snippests): After upgrading Openshift cluster to 4.4.13 customer is seeing intermittent mount time outs for all PVs provisioned via OCS. 


Version of all relevant components (if applicable):
Openshift 4.4.13


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Developers on the cluster cannot deploy applications that consume OCS storage. We have been able to reproduce this with each of their 4 storage classes all managed by OCS. 


Is there any workaround available to the best of your knowledge?
Not that we can find. 


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
Unknown


Is this issue reproducible?
Yes


Can this issue reproduce from the UI?
Yes


If this is a regression, please provide more details to justify this:
Unknown

Steps to Reproduce:
1. Deploy new application
2. Wait ~90 seconds
3. See 'mount timeouts' in the deployment logs. 


Actual results:
Mounts timeout for deployments


Expected results:
Deployments succeed. 


Additional info:


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