Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-4589

vector fails to start on a node with IPv6 disabled

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Hide
      Prior to this fix, vector failed to start on IPv4-only nodes, failing to create a listener for its metrics endpoint with an error "Failed to start Prometheus exporter: TCP bind failed: Address family not supported by protocol (os error 97)".
      With the fix, vector operates normally on IPv4-only nodes.
      Show
      Prior to this fix, vector failed to start on IPv4-only nodes, failing to create a listener for its metrics endpoint with an error "Failed to start Prometheus exporter: TCP bind failed: Address family not supported by protocol (os error 97)". With the fix, vector operates normally on IPv4-only nodes.
    • Bug Fix
    • Done
    • Log Collection - Sprint 243, Log Collection - Sprint 244, Log Collection - Sprint 245

    Description

      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

      {component_kind="sink" component_id=prometheus_output component_type=prometheus_exporter component_name=prometheus_output}

      : 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.

      Attachments

        Issue Links

          depends on

          Bug - A problem that impairs or prevents the functions of the product. LOG-4608 [httpserver] Connection refused on IPv6 cluster

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. LOG-4593 vector fails to start on a node with IPv6 disabled

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. LOG-3440 [vector] no data point on collection dashboard on IPv6 single stack

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link Collector pods fails to start on nodes with IPv6 disabled

          GitHub openshift/cluster-logging-operator#2200: LOG-4589: vector fails to start on a node with IPv6 disabled

          GitHub openshift/cluster-logging-operator#2201: LOG-4589: vector fails to start on a node with IPv6 disabled

          Web Link RHBA-2023:124593 Logging Subsystem 5.7.9 - Red Hat OpenShift

          mentioned on

          GitLab Merge request - Updated US source to: 38f1d90 Merge pull request #2186 from vparfonov/log4383

          GitLab Merge request - Updated US source to: 78a1e1a Merge pull request #2200 from syedriko/syedriko-log-4589

          Activity

            People

              syedriko_sub@redhat.com Sergey Yedrikov
              syedriko_sub@redhat.com Sergey Yedrikov
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: