We did not cause your MySQL upgrade. We do not provide MySQL, and never have (not in VM6, not in pre-VM6 and not in VM7). MySQL has never come from us. And, MariaDB, our new default DB on all supported distros, also does not come from us and never will. You chose an OS (and maybe some other third party repositories), and we respect that choice.
Virtualmin offers to update from whatever repositories you have configured. If you’ve configured a repo that will change major versions of the database, that’s out of our control (and wildly dangerous…no Linux distro does that, as far as I know, so I’m not sure how you would have gotten there without knowing you were going there). Only a major OS upgrade should change the database version, and you should prepare for that major change, following the docs provided by your OS vendor and the database developers.
I also want to mention that Virtualmin virtual-server module reached version 7.x last year…if you’re just now updating, you were months out of date. That’s a bad idea. But Virtualmin does not automatically update! We provide a list of available updates and button you can click to install them (after reviewing them, of course). There are packages that provide automatic updating on Ubuntu, but we do not install them as part of the Virtualmin install.
I’m sorry you have had an issue with your database, and we’ll try to help when we can (even with stuff unrelated to our software), but you’re dumping a lot of stuff on us that we simply don’t do, and that’s really frustrating. It’s difficult to help when the problem is being presented as “here’s all the ways you broke my server”, when literally none of it was us.
If there are other unrelated outstanding issues you need help with (or want to report), we’re happy to talk about it in a new topic. I have to insist on the “one problem per topic” rule. Forum Guidelines: Please read before posting!