maintenance container seems to not recognize installed shopware version

[einz-loggik]

Hi,

i hope someone can help me. I have a problem with our shopware deployment on our dev server.
It seems that the maintenance container is not recognizing the installed shopware version correctly. It always tries to run all migrations and then runs into an error because the language table already exists.

0/541 [░░░░░░░░░░░░░░░░░░░░░░░░░░░░]   0% < 1 sec/< 1 sec 133.0 MiB ---------- ---------------------- 
Action     Number of migrations  
---------- ---------------------- 
Migrated   0 out of 541          
In MigrationCommand.php line 165:
[Shopware\Core\Framework\Migration\Exception\MigrateException]               
Migration error: An exception occurred while executing '                     
            CREATE TABLE `language` (                                        
              `id`                  BINARY(16)                               
        ':                                                                   
            ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode  
_ci;                                                                         
SCADE                                                                        
              CONSTRAINT `fk.language.parent_id` FOREIGN KEY (`parent_id`)   
                REFERENCES `language` (`id`) ON DELETE CASCADE ON UPDATE CA  
ustom_fields`)),                                                             
              CONSTRAINT `json.language.custom_fields` CHECK (JSON_VALID(`c  
ent_id`),                                                                    
              KEY `idx.language.language_id_parent_language_id` (`id`, `par  
              KEY `idx.language.translation_code_id` (`translation_code_id`  
),                                                                           
              UNIQUE `uniq.translation_code_id` (translation_code_id),       
              PRIMARY KEY (`id`),                                            
 NOT NULL,                                                                   
              `name`                VARCHAR(50) COLLATE utf8mb4_unicode_ci   
              `parent_id`           BINARY(16)                               
 NULL,                                                                       
              `locale_id`           BINARY(16)                               
              `translation_code_id` BINARY(16)                               
              `custom_fields`       JSON                                     
              `created_at`          DATETIME(3)                              
              `updated_at`          DATETIME(3)
SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'language' already exists

I only noticed it because i tried to change the shopware version...
The same setup runs on my local machine and there it works perfectly fine.

Get collection for identifier: "core"
migrate Migrations
    0 [░░░░░░░░░░░░░░░░░░░░░░░░░░░░] < 1 sec 141.0 MiB

 ---------- ---------------------- 
  Action     Number of migrations  
 ---------- ---------------------- 
  Migrated   0 out of 0            
 ---------- ---------------------- 

all migrations for identifier: "core" executed

Can someone tell me how the check for an existing shopware installation works?

[shyim]

Hey,

It's fine that it runs all migrations. It should run only the missing ones. Can you check that migration table in the database? It's someting not right with that one

[einz-loggik]

Thats the problem, the update column in the migration table is nearly completely empty. That explains why it tries to run all the migrations.
Seems like it ran some migrations when i set it up on the dev server and then failed? I am not sure what happened.
Is there a way to update the migration table without setting the update dates manually?