-
Bug
-
Resolution: Done-Errata
-
Normal
-
Logging 5.7.6
-
False
-
None
-
False
-
NEW
-
ASSIGNED
-
-
Bug Fix
-
Done
-
-
-
Log Collection - Sprint 243
Description of problem:
On an IPv4-only cluster, vector fails to start, with the following error:
2023-09-29T17:03:26.734456936Z 2023-09-29T17:03:26.734384Z ERROR sink
: vector::sinks::prometheus::exporter: Failed to start Prometheus exporter: TCP bind failed: Address family not supported by protocol (os error 97)
Version-Release number of selected component (if applicable):
5.7.6
How reproducible:
Always
Steps to Reproduce:
- Deploy Logging Operator
- Create a CLF collecting logs to the default log storage
Actual results:
Vector fails to start with the "TCP bind failed: Address family not supported by protocol (os error 97)" error message.
Expected results:
Vector operates normally
Additional Notes
It takes setting the ipv6.disable=1 kernel boot parameter to reproduce this issue.
- clones
-
LOG-4589 vector fails to start on a node with IPv6 disabled
- Closed
- relates to
-
LOG-3440 [vector] no data point on collection dashboard on IPv6 single stack
- Closed
- links to
-
RHBA-2023:6139 Logging Subsystem 5.8.0 - Red Hat OpenShift
- mentioned on