Project

General

Profile

Bug #2423

cn.resolve() chokes on bad nodeIdentifiers

Added by Rob Nahf over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Robert Waltz
Category:
d1_cn_service
Start date:
Due date:
% Done:

100%

Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:

Description

In the event of a bad NodeReference in the systemmetadata, the desired behavior for resolve is to return at least the valid choices, and redact or include the bad ones it discovered. Currently, it gives up, returning a ServiceFailure instead.

ServiceFailure: 4150:: unregistered Node identifier (DEMO2) in systemmetadata document for object: MNReplicationIT.2012188036391

History

#1 Updated by Rob Nahf over 12 years ago

  • Category set to Metacat
  • Assignee set to Chris Jones

#2 Updated by Chris Jones over 12 years ago

  • Assignee changed from Chris Jones to Robert Waltz

#3 Updated by Robert Waltz over 12 years ago

  • Category changed from Metacat to d1_cn_service
  • Status changed from New to Closed

redact the entry from objectLocationList if node is nonexistent or its state is not UP

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)