[MGNLWORKFLOW-187] magnolia-workflow module cannot be updated when upgrading Magnolia from 4.5.x to 5.2.1 Created: 08/Jan/14  Updated: 05/Feb/14  Resolved: 27/Jan/14

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: 5.2.1
Fix Version/s: 5.2.2, 5.3

Type: Bug Priority: Neutral
Reporter: Magnolia International Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
Issue Links:
Relates
relates to MGNLWORKFLOW-180 Remove permissions for no longer exis... Closed
relates to MGNLWORKFLOW-193 magnolia-workflow module does not ins... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: migration_to_5.2.2

 Description   

When upgrading a Magnolia environment from the version 4.5.x to 5.2.1, the workflow module throws a UUID conflict:

4fd7ab63-7fff-4a27-b16a-ef727cc6a75d in userroles.workflow-base

When upgrading a Magnolia environment from the version 5.1 to 5.2.1, there is no UUID conflict and the workflow module is correctly installed.

See stacktrace attached



 Comments   
Comment by Magnolia International [ 08/Jan/14 ]

THere is a workaround: You can use a lower version of the workflow module such as 5.1.1. If you need some fixes/features which are available in 5.2.1, you can update the module in a second phase. This will work since Magnolia will be in 5.2.1

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