Kodi tries opening the database corresponding to it current version and if it doesn’t find that it starts looking for older versions in order. Once it finds one it will then attempt to convert it to current. This is how it has always worked. I don’t think there is a bug here. Perhaps your SQL server was slow to respond on this particular boot and it didn’t connect until after it had already tried and failed with 121 and 119. In any event it looks like you had already found the solution which is to just drop the newest database and let it have another go.
I can confirm since I’m the one who figured that one out
And even figured out a remote mapping that allows you to use the play button on a remote in this screen.