-
Bug
-
Resolution: Fixed
-
Neutral
-
6.0
-
None
Steps to reproduce
1. Set up a Magnolia instance version 6.1.5. You will need to exclude personalization related modules, see 615exclusions_DXnoPersonalization.xml
2. Migrate to 6.2, some more modules related to personalization will need to be excluded. See 62exclusions_DXnoPersonalization.xml
3. Start the instance to proceed with the migration.
Expected results
The migration process ends without issues
Actual results
There is an exception and the instance is not properly migrated:
020-04-30 11:40:53,690 ERROR info.magnolia.module.InstallContextImpl : [163/312 tasks - Magnolia Workflow Pages Integration Module (version 6.0.0)]> Error while installing or updating workflow-pages module. Task 'Bootstrap' failed. (ItemExistsException: a node with uuid 0d74c8b7-6660-4bac-b027-2538fd46aabf already exists!) java.lang.RuntimeException: java.lang.RuntimeException: Error importing /mgnl-bootstrap/workflow-pages/config.modules.pages-app.messageViews.xml: a node with uuid 0d74c8b7-6660-4bac-b027-2538fd46aabf already exists!
Workaround
Remove conflicted config node before migrating.
Development notes
It seems related to pages app. If we check the configuration in 6.1.5 and look that concrete UUID we will see that it is associated to path /modules/pages/messageViews.
So it seems that some of the excluded modules is moving or deleting this configuration. Theorically, this configuration should not be related to personalization.
- is related to
-
WORKFLOWEX-2 Pages message view changed locations
- Closed