[MGNLSYNC-38] Magnolia Upgrade 5.5.x to 5.6.x fails due to uuid collision Created: 05/Apr/18 Updated: 29/Mar/22 Resolved: 14/Mar/22 |
|
| Status: | Closed |
| Project: | Magnolia Synchronization Module |
| Component/s: | None |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Matthias Müller | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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
|
| Visible to: |
Rihard Monovic
|
| Team: |
| Description |
|
Upgrading Magnolia 5.5.9 to 5.6.3 fails due to the following errors
These nodes already exist in the config workspace, but (probably because the module was split into submodules) magnolia tries to bootstrap the XMLs in the mgnl-bootstrap/synchronization-app folder again => UUID-Collision
Workaround Exporting the mentioned node from the configuration workspace and re-import it after the update (if custom changes were made)
Suggested fix Remove the Bootstrap-Files from the synchronization-app folder (so they are no longer automatically bootstrapped) and create a custom defensive installation task, which only runs, if the node doesn't exist yet. |