Hi, Does anyone know who to contact to report problems with telemetry.ceph.com?
After a reasonably successful update of my cluster, I received a HEALTH_WARN [Telemetry requires re-opt-in] even though I had already re-approved telemetry. While trying to understand the problem, I stumbled across the fact that although the host telemetry.ceph.com has an IPv4 and an IPv6 address, I cannot reach it because IPv6 only has a dropping firewall or something similar attached to it. Now, I can configure a proxy that also reaches the legacy Internet, but it also tried to reach IPv6 first, so that currently no IPv6-enabled Ceph cluster should be visible in the telemetry. My workaround would now be to overlay telemetry.ceph.com on the DNS cache... but that's just a hack. ----- raw shell output for reproduction ----- > host telemetry.ceph.com telemetry.ceph.com has address 8.43.84.137 telemetry.ceph.com has IPv6 address 2620:52:3:3:201a:4aff:feab:8409 > telnet 2620:52:3:3:201a:4aff:feab:8409 80 Trying 2620:52:3:3:201a:4aff:feab:8409... telnet: Unable to connect to remote host: Connection timed out > telnet 8.43.84.137 80 Trying 8.43.84.137... Connected to 8.43.84.137. Escape character is '^]'. get / HTTP/1.0 HTTP/1.1 302 Found Location: https://telemetry.ceph.com/ _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
