-
Ticket
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
-
False
-
-
-
Rox Sprint 4.9I - Global
CUSTOMER PROBLEM
The secured clusters are reported as unhealthy. To resolve the issue, the instance was recreated in OCP and new init-bundles were created. However, the issue remains unresolved, and the clusters that were deleted in the RHACS UI for this procedure are no longer being displayed. This is errors reported in pods logs in the sensor:
2025-09-30T18:07:44.430919253Z # Failed to fetch centrals TLS certs: verifying tls challenge: validating certificate chain: using a certificate bundle that was generated from a different Central installation than the one it is trying to connect to: x509: certificate signed by unknown authority ... 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 central cluster and the secured cluster are in version 4.8.2.
- is triggering
-
ROX-31172 Misleading Sensor logs on TLS connection failure to Central
-
- To Do
-