Project

General

Profile

Story #7889

Synchronization not happening when authoritativeMN is not set correctly.

Added by Rob Nahf about 5 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
d1_synchronization
Target version:
Start date:
2017-07-19
Due date:
% Done:

0%

Story Points:

Description

This leads to an uncorrectable situation because system metadata updates can only happen from the authoritativeMN. We need to add validation upon first synchronization such that the authoritativeMN is a registeredMN, even if it is not really present (state=down).


Subtasks

Task #8150: Enable CN certificate to alter authoritativeMN property in SystemMetadataNewJing Tao

Task #8151: CNs should verify that the authoritativeMN listed in SystemMetadata is a valid MNNewJing Tao

History

#1 Updated by Rob Nahf about 5 years ago

  • Subject changed from Synchronization happening when authoritativeMN is not set correctly. to Synchronization not happening when authoritativeMN is not set correctly.

#2 Updated by Rob Nahf about 5 years ago

  • Assignee changed from Robert Waltz to Rob Nahf

#3 Updated by Laura Moyers about 5 years ago

On initial harvest of an object, there should be validation of the authoritativeMemberNode and originMemberNode, as in:
validate that the aMN and oMN are properly formed (check for urn pattern), and
validate that the aMN and oMN are registered MNs (status up/down doesn't matter)

Question: Are there any other validations that need to occur for aMN and oMN?

Comment: Back in the day, there was a reason for not validating aMN/oMN. If anyone can recall what that reason was, and determine if adding this sort of validation will cause a conflict, that'd be helpful.

#4 Updated by Dave Vieglais over 4 years ago

  • Target version set to CCI-2.4.0

#5 Updated by Dave Vieglais almost 4 years ago

  • Sprint set to Infrastructure backlog

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)