Project

General

Profile

Actions
Copy link

Bug #6938

closed

MNStorage.create() doesn't set sysmeta "authoritativeMemberNode" field if not already set by client

Added by Peter Slaughter almost 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
ben leinfelder
Category:
-
Target version:
2.6.0
Start date:
01/12/2016
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:

Description

If authoritativeMemberNode element is not set in the sysmeta submitted with an object during create() the MN doesn't set it, leading to the object or metadata not being able to be updated.
This is the case with https://mn-stage-ucsb-2.test.dataone.org/knb/d1/mn/v2/meta/urn:uuid:c8b42a90-7dd7-4dcc-a005-84a5cd26354c , which can't be updated or have it's sysmeta
updated. When this is attempted, the error is printed:

Error updating urn:uuid:c8b42a90-7dd7-4dcc-a005-84a5cd26354c: Coudn't find the authoritative member node in the system metadata associated with the pid urn:uuid:c8b42a90-7dd7-4dcc-a005-84a5cd26354c

Actions
Copy link

Also available in: Atom PDF