•  
      request #37555 Unexpected ordering of forge upgrade buckets
    Infos
    #37555
    Joris MASSON (jmasson)
    2024-04-04 20:00
    2024-04-04 14:51
    39148
    Details
    Unexpected ordering of forge upgrade buckets

    One of the forge upgrade buckets for the project_file_upload, named b2024003071430_add_project_to_project_file_upload_table, has a typo in its datetime naming b202400, which is taken into account by the upgrade system. It is ordered at the very beginning and applies first. However, another forge upgrade bucket named b202402131221_add_project_file_upload_table does not expect the table to exist and fails.

    Since we mark forge upgrade buckets that have already been run (to avoid running them more than once) based on their name, we should probably not rename the first bucket. Instead, we will change b202402131221_add_project_file_upload_table so that it "does nothing", because the table is already created with the correct columns by b2024003071430_add_project_to_project_file_upload_table.

    This should solve issues at Tuleap upgrades like the following:

    [error] SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'project_file_upload' already exists
    
    Upgrade process
    15.6
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Joris MASSON (jmasson)
    Closed
    2024-04-04
    Attachments
    Empty
    References
    Referencing request #37555

    Follow-ups