Uploaded image for project: 'Folio Automation Testing'
  1. Folio Automation Testing
  2. FAT-958

API Integration Test Environment Build Fails due to Duplicate Barcode

    XMLWordPrintable

Details

    • DevOps Sprint 122, DevOps Sprint 123
    • FOLIO DevOps

    Description

      Earlier today, VRohach reported that the API integration test build were failing.

      The logs for the latest builds contain:

      ERROR:  could not create unique index "item_barcode_idx_unique"
DETAIL:  Key (lower(jsonb ->> 'barcode'::text))=(2294890831) is duplicated.

      This suggests that there are duplicate item barcodes within the data set used for these tests:

      https://s3.amazonaws.com/folio-public-sample-data/perf.tar.gz

      This used to be acceptable until MODINVSTOR-523 was implemented.

      Running the SQL query suggested in the release notes shows that perf.tar.gz has 421 barcodes that are used two times (and no barcode that is used more than two times). One of the duplicate barcodes is 2294890831.

      Interested Parties
      julianladisch - developer of the change
      jakub - Lead of the CP team and member of Capacity Planning
      Emelianov - Lead for API integration testing
      malc ian wayne dcrossley - DevOps folks

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Task - A task that needs to be done. FAT-947 mod-data-import: Set up default data for data-import integration tests

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is duplicated by

            Bug - A problem which impairs or prevents the functions of the product. FAT-959 API Karate pipeline is failing

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. FAT-961 mod-oai-pmh duplicate item barcode 326547658598

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Tech Debt - MODINVSTOR-523 Item barcode should be unique

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                hleb_surnovich Hleb Surnovich
                marcjohnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases