[MODSOURMAN-870] Error while updating module after fix for schema differences between MG Bugfest and clean MG deployment - FOLIO Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: P2
Resolution: Done
Affects Version/s: None
Fix Version/s: 3.4.4
Labels:
- data-import
- epam-folijet

Template:
Sprint:
Folijet Sprint 148
Story Points:
1
Development Team:
Folijet
Release:
Morning Glory (R2 2022) Bug Fix
Epic Link:
Batch Importer (Bib/Acq)
RCA Group:
Lack of testing

Description

While updating mod-source-record-manager Bugfest from 3.4.2 to 3.4.3 there is an error:

{ "id" : "mod-source-record-manager-3.4.3", "from" : "mod-source-record-manager-3.4.2", "action" : "enable", "message" : "Tenant operation failed for module mod-source-record-manager-3.4.3: SQL error\n CREATE TRIGGER set_id_in_jsonb BEFORE INSERT OR UPDATE ON job_execution_source_chunks FOR EACH ROW EXECUTE PROCEDURE set_id_in_jsonb();\nERROR: trigger \"set_id_in_jsonb\" for relation \"job_execution_source_chunks\" already exists (42710)", "stage" : "invoke" }

It seems like this appears for newly added scripts in scope of: ~~MODSOURMAN-833~~

TestRail: Results

Attachments

Issue Links

blocks

MODSOURMAN-871 Release v3.4.4 (R2 MG bugfix)

Closed

defines

UXPROD-3464 NFR: Data Import R2 2022 Morning Glory Support Bug work

Closed

relates to

MODSOURMAN-833 Schema differences between MG Bugfest and clean MG deployment: mod-source-record-manager

Closed

Activity

People

Assignee:: Volodymyr Rohach

Reporter:: Volodymyr Rohach

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 06/Sep/22 11:54 AM

Updated:: 08/Sep/22 11:03 AM

Resolved:: 06/Sep/22 12:56 PM

Error while updating module after fix for schema differences between MG Bugfest and clean MG deployment