Uploaded image for project: 'mod-source-record-manager'
  1. mod-source-record-manager
  2. MODSOURMAN-940

DI Jobs stuck when selecting a wrong profile

    XMLWordPrintable

Details

    • 0
    • Folijet
    • Orchid (R1 2023)
    • Not a bug
    • Orchid (R1 2023), Nolana (R3 2022)

    Description

      Overview:  When select a wrong profile (that doesn't work with the input MARC file), the job is stuck at 0%.  Cancelling the job and launching new jobs also yield the same result, all subsequent jobs get stuck at 0%. 

      Current workaround: Delete all messages from Kafka's DI topics

      Steps to Reproduce:

      1. Go to the Data Import app
      2. Upload a MARC Authority file 
      3. Choose a profile that doesn't work with MARC Authority: e.g. the Default Create MARC Bib and Instance job profile or one that creates items, holdings, and instances.

      Expected Results: Either the job fails immediately upon validation of the record type with the chosen profile, or user can cancel the job successfully, and then subsequent jobs can be run normally.

      Actual Results: All jobs, current and subsequent new ones, get stuck at 0%

      Additional Information: This problem is easily reproducible.  It has been an issue up to now in the Nolana release. 

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-3727 NFR: Data Import Support Bug work (Orchid R1 2023)

            • P2 - normal priority level, must be included in the current development cycle
            • In progress
            relates to

            Bug - A problem which impairs or prevents the functions of the product. MODDICONV-292 Add validation of Folio Record Type upon linking of Action and Mapping profile

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

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-859 DI stops processing the following files after using an incorrect type of JobProfile

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

            Task - A task that needs to be done. MODSOURMAN-899 Do not process chunks when the DI job is stopped

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODDICONV-214 Import stops if profiles were incorrectly set-up - DRAFT

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSOURMAN-956 Stop processing the job with incorrect profile

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

            Activity

              People

                Kateryna Senchenko Kateryna Senchenko
                mtraneis Martin Tran
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases