Project

General

Profile

Bug #6938

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

Added by Peter Slaughter over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
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

History

#1 Updated by ben leinfelder over 4 years ago

  • Assignee set to ben leinfelder
  • Status changed from New to In Progress

Now setting authMN to origin MN if not already set by client

#2 Updated by ben leinfelder over 4 years ago

  • Status changed from In Progress to Closed

committed to trunk - can be deployed to a MN for testing if you'd like.

Also available in: Atom PDF