Closed pavolloffay closed 2 months ago
For me "query-frontend" pod remained in CrashLoopBackOff
.
pod/tempo-gi-query-frontend-6b5bff6dd4-4tj8w 2/3 CrashLoopBackOff 36 (2m3s ago) 161m
with below error
oc logs pod/tempo-gi-query-frontend-6b5bff6dd4-4tj8w oauth-proxy
2024/10/16 15:13:27 main.go:145: unable to decode review: invalid character 's' looking for beginning of value
For me "query-frontend" pod remained in
CrashLoopBackOff
.pod/tempo-gi-query-frontend-6b5bff6dd4-4tj8w 2/3 CrashLoopBackOff 36 (2m3s ago) 161m
with below error
oc logs pod/tempo-gi-query-frontend-6b5bff6dd4-4tj8w oauth-proxy 2024/10/16 15:13:27 main.go:145: unable to decode review: invalid character 's' looking for beginning of value
Can you open a separate issue and post your TempoStack
CR?
For me "query-frontend" pod remained in
CrashLoopBackOff
.pod/tempo-gi-query-frontend-6b5bff6dd4-4tj8w 2/3 CrashLoopBackOff 36 (2m3s ago) 161m
with below error
oc logs pod/tempo-gi-query-frontend-6b5bff6dd4-4tj8w oauth-proxy 2024/10/16 15:13:27 main.go:145: unable to decode review: invalid character 's' looking for beginning of value
Can you open a separate issue and post your
TempoStack
CR?
I think issue was related to this one only.
After disabling / removing route from CR , CrashLoopBackOff
stopped. I was using Redhat Official Operator on Openshift 4.14.36.
For me "query-frontend" pod remained in
CrashLoopBackOff
.pod/tempo-gi-query-frontend-6b5bff6dd4-4tj8w 2/3 CrashLoopBackOff 36 (2m3s ago) 161m
with below error
oc logs pod/tempo-gi-query-frontend-6b5bff6dd4-4tj8w oauth-proxy 2024/10/16 15:13:27 main.go:145: unable to decode review: invalid character 's' looking for beginning of value
Can you open a separate issue and post your
TempoStack
CR?I think issue was related to this one only.
After disabling / removing route from CR ,
CrashLoopBackOff
stopped. I was using Redhat Official Operator on Openshift 4.14.36.
unable to decode review: invalid character 's' looking for beginning of value
sounds like a typo in the sar
value of the CR, that's why we need the entire CR to be able to debug this issue. This issue is about infinite reconciliation, the issue you posted is about a crash loop. The area of the error might be the same, but the root cause is different.
The secret tempo-simplest-cookie-proxy keeps updating, only the resource version