[stable/redis] Can't open the append-only file: No such file or directory

[Efp95]

Describe the bug
There's been a persistent volume I was using for Redis and it's been working as expected.
Recently, I got several restarts from my Redis pod due to the liveness probe.

According to what I saw in the container logs the restarts occur when the "Can't open the append-only file: No such file or directory"
There were 2 times that the pod kept restarting over and over.
A "workaround" was to delete my PersistentVolumeClaim and the Pod so the StatefulSet create others.

And one last thing, we have around 6 Redis pods deployed separately with the same configuration.
This issue occurred only for one of them (pod kept restarting).
There were also restarts for the other instances of Redis but they got up & running after a couple of restarts

Version of Helm and Kubernetes:
kubernetes v1.15.7
helm v2.13.1

Which chart:
stable/redis v8.0.10

What happened:
Redis pod keeps restarting due to LivenessProbe (as first error description, then it shows up as CrashLoopBackOff).

What you expected to happen:
Pod gets up & running (after a restart maybe)

How to reproduce it (as minimally and precisely as possible):
I haven't identified repro steps. It has happened in our NONPROD and PROD clusters.

Anything else we need to know:
This is the config I've been using:

  usePassword: true
  password: "*********"
  nameOverride: appredis
  cluster:
    enabled: false
  master:
    statefulset:
      updateStrategy: RollingUpdate
    persistence:
      size: 1Gi
      storageClass: azurefile

And here you have and attachment from the log producing the error

[carrodher]

Hi,

Given the stable deprecation timeline, this Bitnami maintained Helm chart is now located at bitnami/charts. Please visit the bitnami/charts GitHub repository to create Issues or PRs.

In this issue, we tried to explain more carefully the reasons and motivations behind this transition, please don't hesitate to add a comment in this issue if you have any question related to the migration itself.

Regards,

[Efp95]

@carrodher Thanks!
I created the same issue for that repo: bitnami/charts#2220