Bug #6938
closedMNStorage.create() doesn't set sysmeta "authoritativeMemberNode" field if not already set by client
0%
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
Updated by ben leinfelder over 8 years ago
- Status changed from New to In Progress
- Assignee set to ben leinfelder
Now setting authMN to origin MN if not already set by client
Updated by ben leinfelder over 8 years ago
- Status changed from In Progress to Closed
committed to trunk - can be deployed to a MN for testing if you'd like.