Bug 2107065 - governance-policy-framework in CrashLoopBackOff state on spoke cluster: Failed to start manager {"error": "error listening on :8081: listen tcp :8081: bind: address already in use"}
Summary: governance-policy-framework in CrashLoopBackOff state on spoke cluster: Faile...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: GRC & Policy
Version: rhacm-2.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: rhacm-2.6
Assignee: Matt Prahl
QA Contact: Derek Ho
Mikela Dockery
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-14 09:01 UTC by Marius Cornea
Modified: 2022-09-06 22:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-06 22:33:43 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.6+
cbynum: rhacm-2.6.z+


Attachments (Terms of Use)
must-gather (614.20 KB, application/gzip)
2022-07-14 09:04 UTC, Marius Cornea
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 24285 0 None None None 2022-07-14 12:03:05 UTC
Red Hat Product Errata RHSA-2022:6370 0 None None None 2022-09-06 22:33:53 UTC

Description Marius Cornea 2022-07-14 09:01:36 UTC
Description of the problem:

On a bare metal spoke cluster deployed via ZTP procedure, governance-policy-framework pod on the spoke cluster is in CrashLoopBackOff state due to:

Defaulted container "spec-sync" out of: spec-sync, status-sync, template-sync
2022-07-14T08:42:50.155Z	info	setup	app/main.go:92	Using	{"OperatorVersion": "0.0.1", "GoVersion": "go1.18.1", "GOOS": "linux", "GOARCH": "amd64"}
2022-07-14T08:42:57.873Z	info	controller-runtime.metrics	logr.2/logr.go:252	Metrics server is starting to listen	{"addr": "0.0.0.0:8384"}
2022-07-14T08:42:57.873Z	error	setup	app/main.go:200	Failed to start manager	{"error": "error listening on :8081: listen tcp :8081: bind: address already in use"}
main.main
	/remote-source/app/main.go:200
runtime.main
	/usr/lib/golang/src/runtime/proc.go:250


Release version:
2.6.0-DOWNSTREAM-2022-07-09-13-09-35

Operator snapshot version:
2.6.0-DOWNSTREAM-2022-07-09-13-09-35

OCP version:
4.11.0-rc.2

Browser Info:

Steps to reproduce:
1. Deploy bare metal spoke cluster via ZTP process
2. Wait for policies to be created on the spoke cluster

Actual results:
Policies are not created. 

Expected results:
Policies are created and the system gets configured.

Additional info:

Attaching must-gather

Comment 1 Marius Cornea 2022-07-14 09:04:39 UTC
Created attachment 1897004 [details]
must-gather

Comment 2 Matt Prahl 2022-07-14 13:41:07 UTC
This will be fixed once a new build is out with this change:
https://github.com/stolostron/governance-policy-addon-controller/pull/60

Comment 3 Marius Cornea 2022-07-26 13:09:11 UTC
I can confirm the issue no longer reproduced with a more recent ACM 2.6 build

Comment 6 errata-xmlrpc 2022-09-06 22:33:43 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: Red Hat Advanced Cluster Management 2.6.0 security updates and bug fixes), 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:6370


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