-
Bug
-
Resolution: Done
-
Major
-
None
-
4.12.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
No
-
None
-
None
-
None
-
AI-38, AI-39
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Assisted service pod remains in CrashLoopBackOff state after cluster creation
Version-Release number of selected component (if applicable):
OpenShift 4.12.41
How reproducible:
100%
Steps to Reproduce:
Set up new cluster with Assisted installer, OpenShift 4.12.41 version. Hardware model: Dell R640 IDRAC firmware: 6.10.30.20
Actual results:
Assisted service pod remains in CrashLoopBackOff state
Expected results:
All pods should be running post cluster creation.
Additional info:
Same setup works in 4.10.56 and 4.12.33 version.
- is related to
-
OCPBUGS-60824 Assisted Service pod terminating and entering CrashLoopBackOff due to runtime error: invalid memory address or nil pointer dereference
-
- New
-
-
ACM-23602 [RHACM 2.14] Assisted Service pod terminating and entering CrashLoopBackOff due to runtime error: invalid memory address or nil pointer dereference
-
- Review
-
-
ACM-24232 [RHACM 2.13] Assisted Service pod terminating and entering CrashLoopBackOff due to runtime error: invalid memory address or nil pointer dereference
-
- Review
-
- links to