[MGNLSYNC-51] Synchronisation may fail when nodes are moved into different sub trees Created: 08/Oct/20 Updated: 29/Mar/22 Resolved: 03/Dec/20 |
|
| Status: | Closed |
| Project: | Magnolia Synchronization Module |
| Component/s: | None |
| Affects Version/s: | 1.9 |
| Fix Version/s: | 1.9.1 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Jorge Franco |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | cs-bk, maintenance | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.25d | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| 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
|
||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||
| Epic Link: | Support | ||||||||||||||||||||||||||||||||||||
| Sprint: | Maintenance 30, Maintenance 31, Maintenance 32, Maintenance 33, Maintenance 34, Maintenance 35, Maintenance 36 | ||||||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||||||||||
| Description |
|
Investigation: initial estimate 3sp Investigation outcome and action taken Failure happens when you move/rename a node between different subtrees. There is a workaround: you can publish by hand the node with problems and then sync again. As there is a workaround, first we are going to improve communication to the user. When user launches synchronization process and there is an error related to this problem, we will send a notification to the user with the error, description of the problem and way to fix manually starting a publish of parent. Later we will review the api way to launch synchronization to give similar information in the response. |
| Comments |
| Comment by Jorge Franco [ 22/Oct/20 ] |
|
It fails when you move/rename a node between different subtrees. There is a workaround, you can publish by hand the node with problems and then sync again. |
| Comment by Jorge Franco [ 22/Oct/20 ] |
|
As there is a workaround, first we are going to improve communication to the user. When user launch synchronization process and there is an error related to this problem, we will send a notification to the user with the error, description of the problem and way to fix manually starting a publish of parent. Later we will review the api way to launch synchronization to give similar information in the response. |
| Comment by Jorge Franco [ 27/Oct/20 ] |
|
Created |
| Comment by Jorge Franco [ 26/Nov/20 ] |
|
Implemented solution:
I have created |
| Comment by Ashraf Khamis [ 14/Dec/20 ] |
|
For 5.7.9 & 6.2.6 release notes: |