I'm using Virtualmin GPL which works pretty flawless. However, during a recent conversion from Sub-Server to a Parent Server, I did come across something which appears to be a bug.
During the conversion process, Virtualmin does not update database credential in the domain configuration file.
This causes all future databases to use the previous user id and name schema from the former parent server.
I have in the midst of troubleshooting the issue, verified this by manually checking the domain's configuration file, and even disabling/deleting all databases, then recreating them to see if the issue resolves itself.
In the end, I was able to correct the issue manually by updating the configuration file, turning off databases, deleting any databases already created, then turning the feature back on and creating a new database.
This is certainly not a life threatening issue, however these kind of bugs if ignored, will eventually start adding up.
Anyways, that's my two cents ;-)
Thanks in advance for your attention to this.