-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
-
Description
In case sensor fails to connect to central due to TLS issues, sensor logs include the following snippet, which is very misleading:
2025-09-30T18:07:45.289981588Z common/sensor: 2025/09/30 18:07:45.289829 central_communication_impl.go:241: Warn: Central is running a legacy version that might not support all current features 2025-09-30T18:07:45.290198651Z common/clusterid: 2025/09/30 18:07:45.290128 cluster_id.go:58: Panic: Invalid dynamic cluster ID value "": no concrete cluster ID was specified in conjunction with wildcard ID "00000000-0000-0000-0000-000000000000". For potential solutions refer to https://access.redhat.com/solutions/6972449 2025-09-30T18:07:45.292333566Z panic: Invalid dynamic cluster ID value "": no concrete cluster ID was specified in conjunction with wildcard ID "00000000-0000-0000-0000-000000000000". For potential solutions refer to https://access.redhat.com/solutions/6972449
The code path responsible for producing this log is taken even though the problem is much more fundamental: Sensor did not even receive a Hello-message from Central, in other words: It is misleading to state that something is wrong with the cluster IDs.
Also, the same is mostly duplicated in the log.
Additionally, regarding the "Central is running a legacy version" – we can most likely drop support for such old centrals anyway, which might help streamlining this flow.
- is triggered by
-
ROX-31098 After updating ACS from 4.6.4 to 4.8.2, some secured clusters are reported as unhealthy and their respective pod sensors are in CrashLoopBackoff
-
- Closed
-
