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

Bug 2012978

Summary:	resizer-kube-rbac-proxy in crashloop backoff in aws-ebs-csi-driver-controller
Product:	OpenShift Container Platform	Reporter:	Ben Parees <bparees>
Component:	Storage	Assignee:	aos-storage-staff <aos-storage-staff>
Storage sub component:	Storage	QA Contact:	Wei Duan <wduan>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	aos-bugs, jsafrane
Version:	4.8
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:	2021-10-12 12:12:02 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 Ben Parees 2021-10-11 18:34:55 UTC

Description of problem:
Canary job failed here:
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.8-e2e-aws-canary/1447120191006707712

due to:

Operator progressing (AWSEBSCSIDriverOperatorCR_AWSEBSDriverControllerServiceController_Deploying): AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverControllerServiceControllerProgressing: Waiting for Deployment to deploy pods


Investigation of why the deployment got stuck shows that when looking at the pods on the cluster:

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.8-e2e-aws-canary/1447120191006707712/artifacts/e2e-aws-canary/gather-extra/artifacts/pods.json


the pod: aws-ebs-csi-driver-controller-84f7579876-jst75

is not ready because the container "resizer-kube-rbac-proxy"

is reporting:
message": "back-off 5m0s restarting failed container=resizer-kube-rbac-proxy pod=aws-ebs-csi-driver-controller-84f7579876-jst75_openshift-cluster-csi-drivers(88640df4-0e87-4918-8c50-aa8e8fb1787d)",
"reason": "CrashLoopBackOff"


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

How reproducible:
rare


Actual results:
one of the aws csi driver containers is in crashloop backoff


Expected results:
containers should not be in crashloop backoff


link to full CI job artifacts:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.8-e2e-aws-canary/1447120191006707712/artifacts/e2e-aws-canary/gather-extra/artifacts/

Comment 1 Jan Safranek 2021-10-12 12:06:17 UTC

The container failed with: 

> failed to listen on secure address: listen tcp 0.0.0.0:9204: bind: address already in use

Something on the node sits on our port.

Comment 2 Jan Safranek 2021-10-12 12:12:02 UTC


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