Fauxton shows “This database failed to load” after pod restarts

[apache]

Fauxton shows “This database failed to load” after pod restarts

[colearendt]

Yes, this sounds just like #78 , and #89 would likely fix / is intended to fix 😄

[jftanner]

Did you ever find a fix for the pod not rejoining the cluster properly? I'm encountering that now.

[willholley]

@jftanner can you share the logs from the pod that isn't joined? If the admin hash is not specified in the helm chart then you may be encountering #7.

[jftanner]

Hi @willholley. It might be #7, but it doesn't happen on pod restart. It only happens when there's a new pod after a helmd upgrade. It seems to be that whenever the helm chart is run, it generates new credentials. (I noticed that the auto-generated admin password changes every time I install I update the helm deployment.) New pods pick up the new credential, but old ones don't. So the workaround I found was to kill all the existing pods after scaling. (Obviously not ideal, but I don't have to do that very often.)

Perhaps #89 will fix it?

Alternatively, I could just define my own admin credentials manually and not have a problem anymore.