[LIVECOPY-220] ItemNotFound in Push Master Changes Created: 04/Aug/20  Updated: 13/Apr/22  Resolved: 26/Aug/20

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: 3.1.1
Fix Version/s: 3.2

Type: Bug Priority: Critical
Reporter: Jesus Alonso Assignee: Jesus Alonso
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones LIVECOPY-218 ItemNotFound bei Push in LiveCopy Closed
Relates
relates to LIVECOPY-312 getReferencedLiveCopyNodeById does no... 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
Date of First Response:
Epic Link: Ext DAMs maintenance & partnership support

 Description   

Unfortunately I'm unable to reproduce the problem. However, I can reproduce the same issue on getReferencedLiveCopyNodeById.

Steps to reproduce:

  1. Create live-copy for travel web.
  2. On the copy site, edit about (/travel0/about)
  3. Create a variant for the jumbotron
  4. Now from the pages tree, select the /travel/about and click on Push Master changes**
  5. It will appear the following logs:
2020-08-05 13:05:18,038 INFO  vecopy.actions.PropagateMasterContentChangesHelper: Checking if childNodes for: /travel0/about should be deleted
2020-08-05 13:05:18,088 ERROR vecopy.actions.PropagateMasterContentChangesHelper: Error changing node order /travel0/about/main/04 prev node: /travel0/about/main/00/variants/variant-0 

The problem is getReferencedLiveCopyNodeById selects /travel0/about/main/00/variants/variant-0 instead of /travel0/about/main/00. This issue caused a ItemNotFoundException under some circumstances.  

AC:

  • No ERROR log appears.

Generated at Mon Feb 12 02:26:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.