Elastic search installation issue - /opt/bitnami/scripts/libfs.sh: line 59: 1: missing directory

[bharani-dasari]

Name and Version

bitnami/elasticsearch 8.3.2-debian-11-r0

What architecture are you using?

amd64

What steps will reproduce the bug?

I am currently trying upgrade/install elasticsearch in cluster mode version 8.3.3-debian-11-r10/8.3.2-debian-11-r0 from bitnami helm charts via cloud-deploy. But I am running below error

elasticsearch-v1-ingest-1 copy-default-plugins] /opt/bitnami/scripts/libfs.sh: line 59: 1: missing directory
elasticsearch-v1-coordinating-0 copy-default-plugins] /opt/bitnami/scripts/libfs.sh: line 59: 1: missing directory

What is the expected behavior?

Pods should be up and running

What do you see instead?

elasticsearch-v1-coordinating-0             0/1     Init:CrashLoopBackOff   6 (2m8s ago)    8m1s
elasticsearch-v1-coordinating-1             0/1     Init:CrashLoopBackOff   6 (2m14s ago)   8m
elasticsearch-v1-data-0                     0/1     Init:CrashLoopBackOff   6 (111s ago)    8m1s
elasticsearch-v1-data-1                     0/1     Init:CrashLoopBackOff

[carrodher]

I'm not able to reproduce your issue using the latest Helm chart (21.0.1, with appVersion: 8.13.2). Could you reproduce it by using the latest version?

[Jancis]

I have the same issue with 21.0.1.

copy-default-plugins /opt/bitnami/scripts/libfs.sh: line 61: 1: missing directory

[dgomezleon]

Hi @Jancis ,

Did it happen on a fresh installation or during an upgrade? Are you using any custom values?

[Jancis]

Fresh install, values below. Don't know if it changes anything but i use it as a subchart, 7.x image works, 6.x and 8.x yields the error above. I did doublecheck there ain't any lingering pv's and pvc's before installation.

elasticsearch:
  image:
    # tag: 6.8.23
    # tag: 7.17.20
    tag: 8.12.1-debian-11-r3
    # tag: 8.6.2
  master:
    replicaCount: 1
  coordinating:
    replicaCount: 1
  data:
    replicaCount: 1
  ingest:
    replicaCount: 1

Update: and I don't think it is relevant in this case, but I have override for elasticsearch.service.name

{{- define "elasticsearch.service.name" -}}
{{ .Release.Name }}-es
{{- end -}}

[dgomezleon]

I see,

It works fine for the latest version (debian-12). For debian-11 I would recommend using the latest released tag 8.12.1-debian-11-r20, to create a custom image with all the changes applied (using it directly you will find this error:

/opt/bitnami/scripts/elasticsearch/entrypoint.sh: line 24: DB_DEFAULT_CONF_DIR: unbound variable

Note that we only release Debian-12 since February.

I hope it helps.

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[adiii717]

broken for me using latest helm chart, here is how to reproduce

clusterName: "mycluster"


master:
  replicaCount: 1
  persistence:
    size: 30Gi
data:
  replicaCount: 1
coordinating:
  replicaCount: 0
ingest:
  replicaCount: 0

image:
  tag: 6.8.23

global:
  kibanaEnabled: true

security:
  enabled: false
  restEncryption: false

kibana:
  elasticsearch:
    security:
      auth:
        enabled: false
      tls:
        enabled: false
        usePemCerts: false
      
plugins: ""