[MGNLSYNC-37] UUID conflict when updating synchronization module from 1.7.x to 1.8.x Created: 23/Feb/18  Updated: 29/Mar/22  Resolved: 27/Feb/18

Status: Closed
Project: Magnolia Synchronization Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.8.2

Type: Task Priority: Critical
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: Kromeriz 135, Kromeriz 136
Story Points: 2
Team: Nucleus

 Description   
2018-02-23 12:38:14,509 ERROR info.magnolia.module.InstallContextImpl           : [171/422 tasks - null]> Could not perform installation: java.lang.RuntimeException: Error importing /mgnl-bootstrap/synchronization-app/config.modules.synchronization-app.apps.xml: a node with uuid 7133771b-fa4c-4f26-bffd-4e9b0781ec47 already exists!
java.lang.RuntimeException: java.lang.RuntimeException: Error importing /mgnl-bootstrap/synchronization-app/config.modules.synchronization-app.apps.xml: a node with uuid 7133771b-fa4c-4f26-bffd-4e9b0781ec47 already exists!
Caused by: javax.jcr.ItemExistsException: a node with uuid 7133771b-fa4c-4f26-bffd-4e9b0781ec47 already exists!

This is caused by splitting synchronization into submodules. New magnolia-synchronization-app tries to bootstrap app into new location, but that already exist in "/modules/synchronization/apps" with same UUID


Generated at Mon Feb 12 07:39:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.