-
Bug
-
Resolution: Done-Errata
-
Major
-
rhos-18.0.4
-
None
-
0
-
False
-
-
False
-
?
-
telemetry-operator-container-1.0.7-1
-
None
-
-
Bug Fix
-
Done
-
-
-
CloudOps 2025 Sprint 2
-
1
-
Important
When telemetry-operator is creating scrapeconfigs, It'll specify targets in this format <host>:<port>. host can be either a hostname or an IP address. if it's an IPv6 IP address, it needs to be wrapped in "[]" before adding the port, which currently doesn't happen. So we have targets like this in IPv6 environments `1111:222:3333:4444:555:666:7:888:9100`, while they should look like this instead: `[1111:222:3333:4444:555:666:7:888]:9100`
The Prometheus WebUI is showing the following logs:
```
Get "https://1111:222:3333:4444:555:666:7:888:9100/metrics": tls: failed to verify certificate: x509: certificate is valid for 1111:222:3333:4444:555:666:7:888, 1111:222:3333:4444:555:666:7:888, 1111:222:3333:4444:555:666:7:888, 1111:222:3333:4444:555:666:7:888, not 1111:222:3333:4444:555:666:7:888: address 1111:222:3333:4444:555:666:7:888:9100: too many colons in address
Get "http://1111:222:3333:4444:555:666:7:888:8888/metrics": dial tcp [1111:222:3333:4444:555:666:7:888]:8888: connect: connection refused: address 1111:222:3333:4444:555:666:7:888:8888: too many colons in address
```
- links to
-
RHBA-2025:146727 Release of containers for RHOSO OpenStack Podified operator