Uploaded image for project: 'mod-data-export'
  1. mod-data-export
  2. MDEXP-571

Migration script fails if upgrading from version 4.4.2 to version 4.5.1

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Duplicate
    • 4.5.1
    • None
    • Ubuntu 20.04 VM

      single server installation

    • Firebird
    • Not Scheduled
    • No
    • Hide
      The error seems to have disappeared after I have manually removed an entry from the mapping_profiles table:
      psql
      SET search_path TO diku_mod_data_export;
      delete from job_profiles where id = '5e9835fc-0e51-44c8-8a47-f7b8fce35da7';
      delete from mapping_profiles where id = '1ef7d0ac-f0a8-42b5-bbbb-c7e249009c13';

      I had to delete one entry from job_profiles, too, because it referenced the entry of the mapping_profiles table.
      Show
      The error seems to have disappeared after I have manually removed an entry from the mapping_profiles table: psql SET search_path TO diku_mod_data_export; delete from job_profiles where id = '5e9835fc-0e51-44c8-8a47-f7b8fce35da7'; delete from mapping_profiles where id = '1ef7d0ac-f0a8-42b5-bbbb-c7e249009c13'; I had to delete one entry from job_profiles, too, because it referenced the entry of the mapping_profiles table.
    • HBZ
    • Not a bug

    Description

      Overview:

      Tenant operation failed for module mod-data-export-4.5.1: SQL error
       INSERT INTO diku_mod_data_export.mapping_profiles(     id, jsonb, creation_date, created_by)   VALUES ('1ef7d0ac-f0a8-42b5-bbbb-c7e249009c13', '{   "id": "1ef7d0ac-f0a8-42b5-bbbb-c7e249009c13",   "name": "Default holdings mapping profile",   "default" : true,   "description": "Default mapping profile for MARC for holdings record",   "recordTypes": [     "HOLDINGS"   ],   "outputFormat": "MARC",   "userInfo": {     "firstName": "System",     "lastName": "Process",     "userName": "system_process"   },   "metadata":{     "createdDate":"2020-07-28T00:00:00Z",     "createdByUserId":"00000000-0000-0000-0000-000000000000",     "createdByUsername":"system_process",     "updatedDate":"2020-07-28T00:00:00Z",     "updatedByUserId":"00000000-0000-0000-0000-000000000000",     "updatedByUsername":"system_process"   } }', NOW(), '00000000-0000-0000-0000-000000000000');
      ERROR: duplicate key value violates unique constraint "mapping_profiles_pkey" (23505) 

      Steps to Reproduce:

      1. Start with a Lotus installation
      2. Deploy Morning Glory backend modules (of platform-complete)
      3. Try to activate Morning Glory modules:  curl -w '\n' -D - -X POST -H "Content-type: application/json" -d @/usr/folio/platform-complete/install.json http://localhost:9130/_/proxy/tenants/diku/install?deploy=false\&preRelease=false\&tenantParameters=loadReference%3Dfalse

      Expected Results:
      curl returns an HTTP 200. Morning Glory modules have been enabled for the tenant. Lotus modules have been disabled for the tenant.

      Actual Results:
      curl returns a 500 : TTP/1.1 500 Internal Server Error
      Content-Type: text/plain
      content-length: 1018      and the error message as displayed in the overview section of this Jira issue.

      Additional Information:

      Interested parties: hbz

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                ikuss Ingolf Kuss
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases