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

Bug 1862050

Summary:	Connection refused on fluentd metrics on IPv6 single stack cluster
Product:	OpenShift Container Platform	Reporter:	Anping Li <anli>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.6	CC:	aos-bugs, jcantril, periklis
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	logging-core
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1936390 (view as bug list)		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:
Bug Depends On:
Bug Blocks:	1839120, 1936390

Description Anping Li 2020-07-30 10:04:27 UTC

Description of problem
The prometheus is binding to ''. which couldn't listen on the IPv6 Address. We should use  bind '::' for IPv6 Single stack Cluster.

Version-Release -Cluster version 
4.6.0

Steps:
1. Deploy cluster logging on IPv6 Single stack cluster
$oc get svc
NAME                               TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)             AGE
cluster-logging-operator-metrics   ClusterIP   fd02::5230   <none>        8383/TCP,8686/TCP   21h
elasticsearch                      ClusterIP   fd02::d600   <none>        9200/TCP            7h50m
elasticsearch-cluster              ClusterIP   fd02::fbe6   <none>        9300/TCP            7h50m
elasticsearch-metrics              ClusterIP   fd02::c64d   <none>        60001/TCP           7h50m
fluentd                            ClusterIP   fd02::df7c   <none>        24231/TCP           7h50m
fluentdserver                      ClusterIP   fd02::ee1d   <none>        24224/TCP           7h53m
kibana                             ClusterIP   fd02::4df    <none>        443/TCP             7h50m
openshift-olm-test-clo             ClusterIP   fd02::a60    <none>        50051/TCP           23h

2. Access the fluentd metrics
#curl -k -H "Authorization: Bearer `oc sa get-token prometheus-k8s -n openshift-monitoring`" -H "Content-type: application/json" https://$fluentd-svc:24231/metrics

 curl -g -6 -k -H "Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IndKODVrU2d0T0lmSjAySWEzWm9zUzNqRUMteU9qOG83MnJSbXJ3NERlSlkifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJvcGVuc2hpZnQtbW9uaXRvcmluZyIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJwcm9tZXRoZXVzLWs4cy10b2tlbi0ydHpteCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJwcm9tZXRoZXVzLWs4cyIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6IjllMmM4YWMzLWE2ZjMtNGJlOS04NjEyLTViZjFiMjkwODMwZCIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpvcGVuc2hpZnQtbW9uaXRvcmluZzpwcm9tZXRoZXVzLWs4cyJ9.bhp55XGjGhqKOwK-JfvN4yralJQonVW4NIUwG21m27GgI6LeInOhjDILnmaysMPj0-16NFL-8EtL7zfVcXlBvmuf_4nwsuL2G-sTu2N-zt3LsdW7Dm99EZ8pFife91vSn7LxBpkiCsNEjnhCEeO0p_zJZg2jyzyXCK-T-KdNR0J_gPnG1zhUNCJSvtFnkNpkC3B9vimo-Jw4-ha_eE99Z5-c07YYYwgsnS8gaIXCgZFuWL-IQYlidt1Rm59YjeyzYk6J13kdV2RxPHItR-82Vku5s6zOMABoUqSWagazEd02p7zKkDgzvD_MoLPocabiGaXivD1BLHkFtmvdJfkVeg" -H "Content-type: application/json" https://[fd02::df7c]:24231/metrics

curl: (7) Failed connect to fd02::df7c:24231; Connection refused

Comment 2 Jeff Cantrill 2020-08-21 14:11:12 UTC

Moving to UpcomingSprint for future evaluation

Comment 6 Anping Li 2020-09-03 01:49:51 UTC

Verified on clusterlogging.4.6.0-202009020131.p0

Comment 8 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