-
Bug
-
Resolution: Done
-
Major
-
None
-
Tracing Sprint # 259, Tracing Sprint # 260, Tracing Sprint # 261
Description of problem:
On OpenShift clusters where the administrators choose to use non-private networks (RFC 1918 and RFC 6598) for the cluster pod network, it is not possible to deploy TempoStack cluster.
Version-Release number of selected component (if applicable):
OpenShift Logging 5.8
How reproducible:
Always
Steps to Reproduce:
- ...
Actual results:
- Crashlooping pods:
$ omc get po -n openshift-tempo-operator NAME READY STATUS RESTARTS AGE tempo-operator-controller-549c5c6c75-jq76f 2/2 Running 0 11d tempo-sample-compactor-c68665f88-dwgnh 0/1 CrashLoopBackOff 13 58m tempo-sample-distributor-c79d8b6df-qxhtm 0/1 CrashLoopBackOff 13 58m tempo-sample-ingester-0 0/1 CrashLoopBackOff 13 58m tempo-sample-querier-6d46976985-25tb2 0/1 CrashLoopBackOff 13 58m tempo-sample-query-frontend-64db8b66b-qrnqn 1/2 CrashLoopBackOff 13 58m
- Services from pods has no endpoints.
- Error message:
$ omc -n openshift-tempo-operator logs tempo-sample-ingester-0 | grep error 2024-07-22T09:35:37.701448589Z level=warn ts=2024-07-22T09:35:37.7014128Z caller=module_service.go:118 msg="module failed with error" module=memberlist-kv err="service memberlist_kv failed: failed to create memberlist: Failed to get final advertise address: no private IP address found, and explicit IP not provided" 2024-07-22T09:35:37.701487894Z level=error ts=2024-07-22T09:35:37.701459607Z caller=app.go:229 msg="module failed" module=memberlist-kv err="service memberlist_kv failed: failed to create memberlist: Failed to get final advertise address: no private IP address found, and explicit IP not provided"
Expected results:
All TempoStack pods required to form a health hash ring advertise IP address from the pod network range. In turn all pods are healthy and normal operations resume.
Additional info:
The issue seems similar to the LokiStack one described on:
KCS: failed to create memberlist no private IP address found" in Loki for OCP 4
