Details
-
Bug
-
Resolution: Not a Bug
-
Blocker
-
None
-
Logging 5.5.0
-
None
-
False
-
None
-
False
-
NEW
-
OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
-
VERIFIED
Description
Loki Gateway pod is throwing TLS handshake error
[kbharti@cube operator]$ oc logs lokistack-dev-gateway-6c46ccff88-z496m gateway | tail -n 2
2022/06/22 09:48:42 http: TLS handshake error from 10.128.2.8:44036: write tcp 10.128.2.46:8080->10.128.2.8:44036: write: connection reset by peer
2022/06/22 09:48:42 http: TLS handshake error from 10.131.0.5:41506: write tcp 10.128.2.46:8080->10.131.0.5:41506: write: connection reset by peer
Steps to reproduce:
1) Deploy Loki Operator from grafana/loki repo using
make olm-deploy REGISTRY_ORG=rhn_support_kbharti VERSION=v0.0.1
2) Create bucket secret for log storage
3) Provision LokiStack CR
apiVersion: loki.grafana.com/v1beta1 kind: LokiStack metadata: name: lokistack-dev namespace: openshift-logging spec: size: 1x.extra-small storage: secret: name: test type: s3 storageClassName: gp2 tenants: mode: openshift-logging rules: enabled: true selector: matchLabels: openshift.io/cluster-monitoring: "true" namespaceSelector: matchLabels: openshift.io/cluster-monitoring: "true"
How reproducible: Always
Expected Result: Loki components should be up and running without any error
Actual Result: LokiGateway is down with TLS handshake error