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

Bug 2080153

Summary:	aws-load-balancer-operator-controller-manager pod stuck in ContainerCreating status
Product:	OpenShift Container Platform	Reporter:	Hongan Li <hongli>
Component:	Networking	Assignee:	aos-network-edge-staff <aos-network-edge-staff>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	mmasters
Version:	4.11
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 11:09:21 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 Hongan Li 2022-04-29 07:00:54 UTC

Description of problem:
aws-load-balancer-operator-controller-manager pod stuck in ContainerCreating status

OpenShift release version:
aws-load-balancer-operator-bundle-container-0.0.1-2
4.11.0-0.nightly-2022-04-26-181148

Cluster Platform:
AWS

How reproducible:
100%

Steps to Reproduce (in detail):
1. fresh install 4.11 cluster
2. ensure the catalogsource with the latest index image (already added aws-load-balancer bundle) is ready
$ oc -n openshift-marketplace get catalogsource/qe-app-registry
NAME DISPLAY TYPE PUBLISHER AGE
qe-app-registry Production Operators grpc OpenShift QE 3h27m

3. Go to Console>OperatorHub page and search aws-load-balancer-operator then install it

Actual results:
aws-load-balancer-operator-controller-manager pod stuck in ContainerCreating status
$ oc -n aws-load-balancer-operator get pod
NAME READY STATUS RESTARTS AGE
aws-load-balancer-operator-controller-manager-656547767c-l6285 0/2 ContainerCreating 0 8m2s

describe pod and shows
Warning FailedMount 20s (x8 over 84s) kubelet MountVolume.SetUp failed for volume "aws-credentials" : secret "aws-load-balancer-operator" not found

Expected results:
1. since aws-credential is already in kube-system namespace, so the operator itself should create the secret.
2. if need user to create the secret, then we should improve the page of operator installation and add prerequisite description for this.

Impact of the problem:

Additional info:
workaround: create the secret manually before install the operator from OperatorHub, e.g
$ oc create secret generic aws-load-balancer-operator -n aws-load-balancer-operator --from-file=credentials=.aws/credentials

note: above credentials is different from the one in kube-system ns.

** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report. You may also mark the bug private if you wish.

Comment 2 Hongan Li 2022-05-05 09:29:34 UTC

Verified with aws-load-balancer-operator-bundle-container-0.0.1-3 and a "Prerequisites for installation" has been added on Console. 

Follow the instruction and the operator doesn't report the issue anymore.

Comment 4 Miciah Dashiel Butler Masters 2022-05-10 19:02:18 UTC

No version of the component has ever shipped yet, so no doc text is needed for fixes to it.

Comment 7 errata-xmlrpc 2022-08-10 11:09: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 (Important: OpenShift Container Platform 4.11.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:5069