Description of problem: The ClusterLogForwarder API couldn't resolve the IP5 Address. For example -> url: '[fd02::ee1d]:24224'. the #ClusterLogForwarder/instance spec: outputs: - name: fluentd-created-by-user type: fluentdForward url: '[fd02::ee1d]:24224' pipelines: #fluent.conf <label @FLUENTD_CREATED_BY_USER> <match **> @type forward <buffer> @type file path '/var/lib/fluentd/fluentd_created_by_user' queued_chunks_limit_size "#{ENV['BUFFER_QUEUE_LIMIT'] || '1024' }" <--snip----> overflow_action block </buffer> <server> host [fd02 port </server> </match> </label> Version-Release number of selected component (if applicable): 4.6 How reproducible: Always Steps to Reproduce: 1. Use IPv6 Address in URL #ClusterLogForwarder/instance spec: outputs: - name: fluentd-created-by-user type: fluentdForward url: '[fd02::ee1d]:24224' pipelines: Actual Result: The ClusterLogForwarder API transfer '[fd02::ee1d]:24224' to '[fd02'. <server> host [fd02 port </server>
This should be fixed by https://github.com/openshift/cluster-logging-operator/pull/533 when it merges. Note that the forwarder requires a valid absolute URL with a scheme, so `[fd02::ee1d]:24224' will not be accepted but `tcp://[fd02::ee1d]:24224' or `tls://[fd02::ee1d]:24224' will (depending on whether you want plain TCP or TLS connection)
PR has been merged, it can be tested.
Verified on clusterlogging.4.6.0-202009020131.p0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6.1 extras update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4198