[LIVECOPY-316] New master content is not pushed to multiple live copies Created: 20/Jun/22  Updated: 20/Jun/22  Resolved: 20/Jun/22

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

Type: Bug Priority: Blocker
Reporter: Roman Groß Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates LIVECOPY-315 New master content is not pushed to m... 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

 Description   

When pushing a new content element, e.g. a new page header, to multiple live copies, the new element appears in only one of the live copies.

Our test page tree is the following:

 
/MASTER/HOME/About
/tenant/HOME_FR/About (HOME_FR is a livecopy of /MASTER/HOME)
/tenant/HOME_US/About (HOME_US is a livecopy of /MASTER/HOME)
 
A new header was added to the simple page /MASTER/HOME/About and pushed to both live copies, but only appears in HOME_FR/About.
 
For the one live copy not receiving the pushed changes we see logged errors like
 

2022-06-14 16:24:34,545 WARN  vecopy.actions.PropagateMasterContentChangesHelper: Got more than 1 candidate for node /MASTER/HOME/About -> [node /tenant/HOME_FR/About, node /tenant/HOME_US/About]. Using node /tenant/HOME_FR/About2022-06-14 16:24:34,545 INFO  vecopy.actions.PropagateMasterContentChangesHelper: Checking if childNodes for: /tenant/HOME_FR/About should be deleted
2022-06-14 16:24:34,551 ERROR vecopy.actions.PropagateMasterContentChangesHelper: Unable to find referenced page for: /MASTER/HOME/About referenced site: /tenant
2022-06-14 16:24:34,552 WARN  vecopy.actions.PropagateMasterContentChangesHelper: Got more than 1 candidate for node /MASTER/HOME/About -> [node /tenant/HOME_FR/About, node /tenant/HOME_US/About]. Using node /tenant/HOME_FR/About
2022-06-14 16:24:34,552 WARN  vecopy.actions.PropagateMasterContentChangesHelper: child page /tenant/HOME_FR/About/content-area does not have the master content identifier
2022-06-14 16:24:34,552 WARN  vecopy.actions.PropagateMasterContentChangesHelper: Cannot find the master node for /tenant/HOME_FR/About/content-area.

The behavior is reproducible on our side and has been tried several times starting with an empty tree structure in the pages app. Please try to reproduce this or give us feedback in case we are using the live copy module in a wrong way.

To us it is a blocker in the attemt to migrate one of our projects from 6.1 to 6.2 where we were using a incubator (demo) livecopy version.

We have also created a ticket here: https://jira.magnolia-cms.com/browse/LIVECOPY-315

BR


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