You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Thomas Kerin (Jira)" <ji...@apache.org> on 2021/10/29 16:35:00 UTC
[jira] [Closed] (FINERACT-1422) Kubernetes start/stop scripts don't
manage mysql password correctly
[ https://issues.apache.org/jira/browse/FINERACT-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Kerin closed FINERACT-1422.
----------------------------------
Resolution: Won't Do
> Kubernetes start/stop scripts don't manage mysql password correctly
> -------------------------------------------------------------------
>
> Key: FINERACT-1422
> URL: https://issues.apache.org/jira/browse/FINERACT-1422
> Project: Apache Fineract
> Issue Type: Bug
> Components: Test
> Environment: minikube, kubernetes 1.18.0
> Reporter: Thomas Kerin
> Priority: Trivial
>
> Hi,
> I am using the kubectl scripts to start and stop fineract + fineractmysql pods. I noticed if I do startup, shutdown, startup, the configuration becomes broken
> This is because the shutdown script deletes the fineract-tenants-db-secret, but not the persistent volume claim which allows the DB state to be persisted. When the startup script is run again, a new password secret is generated but it won't match the password stored in the database.
> I suspect it was intended that the shutdown script should not delete the data. However in that case, it should not delete the password.
> I believe a possible fix would be:
> * shutdown: should not delete the secret
> * startup: should only create the secret if it does not already exist
> * add delete script to completely erase the entire install - including data and password
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)