Bug 1876933

Summary:	No useful message after hitting volume attachment limit
Product:	OpenShift Container Platform	Reporter:	Jan Safranek <jsafrane>
Component:	Storage	Assignee:	Jonathan Dobson <jdobson>
Storage sub component:	Kubernetes	QA Contact:	Rohit Patil <ropatil>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, jsafrane, piqin, ropatil, xtian
Version:	4.6
Target Milestone:	---
Target Release:	4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1876886	Environment:
Last Closed:	2023-01-17 19:46:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1876886
Bug Blocks:

Description Jan Safranek 2020-09-08 14:37:00 UTC

+++ This bug was initially created as a clone of Bug #1876886 +++

Description of problem:
Max attached ebs volume number is counted separately for csi driver and in-tree plugin, it will make a pod is scheduled successfully, but hang on the volume attachment.

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-09-07-210458

How reproducible:
Always

Steps to Reproduce:
1. Launched a 4.6 Cluster on OCP
2. Created 25 PVCs provisioned by ebs.csi.aws.com
3. Created a Pod(pod1) consumming these PVCs and scheduled this pod to worker1
4. Create 25 PVCs provisioned by kubernetes.io/aws-ebs, after pod1 is running
5. Created a Pod(pod2) consumming these PVCs and scheduled this pod to worker2

Actual results:
pod2 is scheduled successfully,but hang on volume attachment

Report the following event repeatly:
Warning  FailedMount             5m5s       kubelet, ip-10-0-74-88.ap-northeast-1.compute.internal  Unable to attach or mount volumes: unmounted volumes=[local20 local9 local10 local16 local5 local19 local21 local2 local3 local8 local25 local11 local1 local18 local22 local14 local6 local7 local23 local4 local13 local15 local12 local24], unattached volumes=[local20 local9 local10 local16 local5 local19 default-token-52hmc local21 local2 local3 local8 local25 local11 local1 local18 local22 local14 local6 local7 local23 local4 local13 local15 local17 local12 local24]: timed out waiting for the condition

Message "timed out waiting for the condition" is not really useful and should be fixed.

Comment 16 errata-xmlrpc 2023-01-17 19:46:21 UTC

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 (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), 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/RHSA-2022:7399