Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1861961

Summary: Could't use IPv6 Address as URL in ClusterLogForwarder
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.6CC: aconway, aos-bugs, jcantril, lvlcek, periklis
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: logging-core
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 15:09:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Anping Li 2020-07-30 03:06:40 UTC
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>

Comment 2 Alan Conway 2020-07-31 17:46:16 UTC
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)

Comment 3 Lukas Vlcek 2020-08-11 14:25:43 UTC
PR has been merged, it can be tested.

Comment 4 Anping Li 2020-09-03 04:47:49 UTC
Verified on clusterlogging.4.6.0-202009020131.p0

Comment 7 errata-xmlrpc 2020-10-27 15:09:31 UTC
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