Synchronization not happening when authoritativeMN is not set correctly.
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).
#3 Updated by Laura Moyers over 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.