Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Readiness probe failing in ES chart 7.15.0 for images 7.16.0 & 7.16.1

See original GitHub issue

Chart version: 7.15.0 Kubernetes version:

Kubernetes provider: E.g. GKE (Google Kubernetes Engine) GKE Helm Version:

Describe the bug:

Readiness probes failing with chart 7.15 and docker images 7.16.0 and 7.16.1

Steps to reproduce:

Deploy helm chart with latest images

Expected behavior:

Provide logs and/or server output (if relevant):

Warning  Unhealthy               38m (x7 over 39m)  kubelet                  Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" )
Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" )
  Warning  Unhealthy  4m32s (x202 over 38m)  kubelet  Readiness probe failed: Elasticsearch is already running, lets check the node is healthy
curl --output /dev/null -k -XGET -s -w '%{http_code}' ${BASIC_AUTH} http://127.0.0.1:9200/ failed with HTTP code 200
sh: 30: [[: not found
sh: 35: [[: not found
sh: 37: [[: not found

Looks like the [[ in the readiness probe script is not compatible with whatever /bin/sh provides in the docker image

Issue Analytics

State:
Created 2 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

jmlrtcommented, Dec 14, 2021

FYI, 7.16.1 and 6.8.21 releases just got released.

These are the versions to use for the log4j fix.

0reactions

MoacirCarloscommented, Dec 14, 2021

Even after the release of version 7.16.1, here it still gives the same bug reported in this issue.

Top Results From Across the Web

Elasticsearch pod in Kubernetes failing for v 7.16.1

We are using Helm chart from GitHub - elastic/helm-charts: You know, for Kubernetes to deploy Elasticsearch & Kibana in AWS EKS cluster ...

Elasticsearch pod readiness probe fails with "message"

This could mean from K8s perspective the pod is running but the ES cluster has failed to form thus it will not respond...

Changelog - curl

schannel: fix memory leak due to failed SSL connection; scripts/delta: count command line options in the new file; sendf: accept zero-length data in ......

Changelog - Nextcloud

The biggest improvements Nextcloud Hub 3 introduces are: Brand new design; Photos 2.0; Talk improvements; Mail 2.0; Contacts organisational chart ...

Readiness probe failing in ES chart 7.15.0 for ... - Python 博客

Readiness probe failing in ES chart 7.15.0 for images 7.16.0 & 7.16.1. Chart version: 7.15.0 Kubernetes version: Kubernetes provider: E.g. GKE (Google ...