-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.20.z
-
None
-
None
-
False
-
-
None
-
Low
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When TALM is installed prior to or at the same time as ACM the controller pod enters the CrashLoopBackoff state with this error in the pod logs:
$ oc logs -n openshift-operators cluster-group-upgrades-controller-manager-v2-67cb6c6469-jlltv
2026-02-13T20:45:57Z ERROR setup unable to start manager {"error": "failed to determine if *v1.ManifestWork is namespaced: failed to get restmapping: unable to retrieve the complete list of server APIs: work.open-cluster-management.io/v1: no matches for work.open-cluster-management.io/v1, Resource="}
main.main
/workspace/main.go:146
runtime.main
/usr/lib/golang/src/runtime/proc.go:283
This is a minor issue and only seen if TALM is installed prior to ACM or there are issues during install which prevent ACM from installing.
Version-Release number of selected component (if applicable):
4.20.1
How reproducible:
100%
Steps to Reproduce:
1. Install TALM prior to ACM, or concurrent with ACM
2.
3.
Actual results:
pod crashes
Expected results:
TALM should not install without ACM or pod should gracefully report status
Additional info:
