Database type mismatch upgrading from 0.4.4 to 0.5.0

[gilzow]

Just tried to upgrade from 0.4.4 of ddev-platformsh to 0.5.0.
In an existing project that already uses ddev, already had ddev-platformsh installed (0.4.4), and where ddev was not currently running, I ran

ddev get platformsh/ddev-platformsh 

ddev downloaded the tarball for 0.5.0, and then informed me:

Using existing PLATFORMSH_CLI_TOKEN.
 
Using existing PLATFORM_PROJECT from project config.yaml.
 
Using existing PLATFORM_ENVIRONMENT from project config.yaml.

It then showed:

could not process pre-install action '#ddev-nodisplay

followed by several lines of bash code. At the end it showed

: exit status 1, output=There is an existing database in this project that doesn't match the upstream database type.
 Please use 'ddev delete' to delete the existing database and retry, or try 'ddev debug migrate-database mariadb:10.4' to migrate the database.

but i cant tell if that is still part of the bash code, or if it is an actual message. The db in the upstream is:

db:
    type: mariadb:10.4

and the db info in .ddev/config.yaml is

database:
  type: mariadb
  version: "10.4"

so there shouldn't be a mismatch.

[gilzow]

❯ ddev version
 ITEM             VALUE                                   
 DDEV version     v1.21.3                                 
 architecture     amd64                                   
 db               drud/ddev-dbserver-mariadb-10.4:v1.21.3 
 dba              phpmyadmin:5                            
 ddev-ssh-agent   drud/ddev-ssh-agent:v1.21.3             
 docker           20.10.8                                 
 docker-compose   v2.10.2                                 
 docker-platform  docker-desktop                          
 mutagen          0.16.0                                  
 os               darwin                                  
 router           drud/ddev-router:v1.21.3                
 web              drud/ddev-webserver:v1.21.3  

[rfay]

: exit status 1, output=There is an existing database in this project that doesn't match the upstream database type.
Please use 'ddev delete' to delete the existing database and retry, or try 'ddev debug migrate-database mariadb:10.4' to migrate the database.

So you had an existing database that didn't match mariadb:10.4- My bet it was a mariadb:10.3 db, which used to be the default. You can find out the actual type of the database with ddev debug get-volume-db-version

The error message tells you several things you can do, but it doesn't tell you what the existing type is. I'd be interested in how you think it can be improved.

[gilzow]

Mariadb is set to 10.4 in .platform/services.yaml and in .ddev.config.platformsh.yaml

❯ ddev debug get-volume-db-version
mariadb:10.4 

[rfay]

I expect this to be a standard problem, but think it's covered in

• Database type/version conflict on config->start->get #58

The debug technique is what you did, and if ddev debug get-volume-db-version and we have the same version in the .ddev/config.platformsh.yaml, then we'll have to chase.

I'm not sure what the situation was here, but let's chase it with ddev debug configyaml and ddev debug get-volume-db-version next time it happens. Closing in favor of #58