-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.21.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Occassionally a nil pointer dereference error is logged in the console backend. It is related to new code where we store the authenticated user in the request context. A helper function `GetUserFromRequestContext` attempts to access the user stored in the request context and cast it to *User type all in one line, but in some cases the user obejct may not be defined, most likely when authentication has failed. We need to make this function nil safe to prevent the runtime error.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- is duplicated by
-
OCPBUGS-65614 runtime error: invalid memory address or nil pointer dereference
-
- Closed
-
- is related to
-
OCPBUGS-59353 Console pod shows panics due to handling some negative user login scenarios not well, including stuck in a quite misleading forever loop
-
- ASSIGNED
-
- links to