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

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

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

Attachments: PNG File image-2022-06-15-15-14-33-378.png    
Issue Links:
duplicate
is duplicated by LIVECOPY-316 New master content is not pushed to m... Closed
supersession
is superseded by LIVECOPY-317 Maintain push functionality when movi... 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:

 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.

 

Edit:

The issue seems to be related only to creating new components. Editing or removing already existing components work without complications.

The steps to reproduce are the following:

  1. In the pages-app: Create the node structure /MASTER/HOME/About, where "About" is a simple page template with header and content
  2. Create the root note /tenants
  3. Make two live copies from the node /MASTER/HOME, renamed them tho HOME_FR and HOME_US
  4. Move the live copies from / (root) inside the /tenants/ node.
  5. Alter smth in /MASTER/HOME/About, e.g. added a header element
  6. Select /MASTER/HOME and use the Action "PUSH master changes incl. subnodes"; alternatively we tried selecting /MASTER/HOME/About and used the action "PUSH master changes"

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