Now that I have tested a bit more, I am happy with the updated Redmine appliance.
Webmin works as I expected - the 'mariadb_admin' user password is randomly (non-interactively) generated on firstboot and added to the Webmin config. So other than logging into Webmin (via 'root') no user interaction is required. The MariaDB Webmin module "just works"!
But more importantly MariaDB survives restarts and/or reboots, no problem. And so Redmine continues to work as it should! Yay :)
Regardless, please feel free to provide any feedback you have.
I've dissected the broken build, comparing before and after the issue becomes apparent. I've compared them with the new working build. Regardless, I'm still not sure why/how the DB issue occurred. All I needed to do to "fix" it was rebuild it. Along why the issue didn't affect any other apps that include MariaDB. I can only assume that there was some random corruption at build time...!?!
TBH, I don't like it when I don't understand why an issue has occurred and/or what it was that fixed it. Regardless, I'm not going to fight it.
Despite it ending up that there was little to do to fix the issue, I also tidied up a few other bits and pieces that I noticed while pulling the appliance apart .
For further detail, please see the code I changed via the pull requests on GitHub:
I have now tested a bit more and I am happy
Now that I have tested a bit more, I am happy with the updated Redmine appliance.
Webmin works as I expected - the 'mariadb_admin' user password is randomly (non-interactively) generated on firstboot and added to the Webmin config. So other than logging into Webmin (via 'root') no user interaction is required. The MariaDB Webmin module "just works"!
But more importantly MariaDB survives restarts and/or reboots, no problem. And so Redmine continues to work as it should! Yay :)
Regardless, please feel free to provide any feedback you have.
I've dissected the broken build, comparing before and after the issue becomes apparent. I've compared them with the new working build. Regardless, I'm still not sure why/how the DB issue occurred. All I needed to do to "fix" it was rebuild it. Along why the issue didn't affect any other apps that include MariaDB. I can only assume that there was some random corruption at build time...!?!
TBH, I don't like it when I don't understand why an issue has occurred and/or what it was that fixed it. Regardless, I'm not going to fight it.
Despite it ending up that there was little to do to fix the issue, I also tidied up a few other bits and pieces that I noticed while pulling the appliance apart .
For further detail, please see the code I changed via the pull requests on GitHub:
Once the changes have been reviewed by a colleague, I'll merge them and build v18.1 of our Redmine appliance. It will be published early next week.
Thanks again to both you guys for all you've done here.