DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2020-06-17T21:49:55ZDataONE Tasks
Redmine CN REST - Story #8864 (New): Sychronization does not register authoritative replica entry correctlyhttps://redmine.dataone.org/issues/88642020-06-17T21:49:55ZChris Jonescjones@nceas.ucsb.edu
<p>When objects are synchronized to the CN, the <code>d1_synchronization</code> component will fetch the system metadata <br>
for each object and will add a <code><replica></code> entry for the origin node (like <code>urn:node:ESS_DIVE</code>, <br>
as well as entries for other copies (for instance for science metadata copied to the CN, <br>
a <code><replica>urn:node:CN</replica></code> will be added.</p>
<p>In some instances, the origin replica instance is not added to the replica list.<br><br>
This causes downstream problems for the <code>d1_replication</code> component because it relies on the origin node <br>
replica entry to be present in order to set up a replication request to a target node. I'm seeing errors like:</p>
<pre>/var/log/dataone/replicate/cn-replication.log.90:[ERROR] 2020-06-04 05:18:30,179 [pool-15-thread-1] (MNCommunication:requestReplication:34) Could not determine replication source node for replication request for pid: ess-dive-eb6cbb22c605506-20200122T170607966. Replication request failed.
</pre>
<p>Looking back in the logs, this is the case for the following objects:</p>
<pre>ess-dive-3947e68e9825233-20180621T213650539
ess-dive-3b8d9f4513e02f9-20180621T214221437
ess-dive-467a6c3dda4dc88-20180621T211148554
ess-dive-51f345daca126f7-20180328T160350610716
ess-dive-53b37ae5d8c0f51-20200219T211634419654
ess-dive-6b688fab5524c46-20200121T210154766
ess-dive-7a31346c154f02b-20200127T155012488
ess-dive-a1fb05cbd903309-20200130T190835651
ess-dive-b420b097851c716-20180523T161714606
ess-dive-ba81a8a8e0bef31-20180727T200828345
ess-dive-bfaf3d6d6fd038c-20180716T154005175903
ess-dive-c2ef5f3af108c9c-20180621T220020545
ess-dive-eb6cbb22c605506-20200122T170607966
ess-dive-f3238db16593de5-20180621T215956950
</pre>
<p>We need to fix this issue in <code>d1_synchronization</code> so replication runs correctly and monthly <br>
replica auditing (done by ESS_DIVE) doesn't flag these issues.</p>
Infrastructure - Story #8796 (New): Various issues with service access after upgrade to 18.04https://redmine.dataone.org/issues/87962019-05-14T23:57:48ZDave Vieglaisdave.vieglais@gmail.com
<p>Users have reported some issues with CNs after upgrades to 18.04. See individual issues for details.</p>
Infrastructure - Story #8782 (New): Upgrade OS to Ubuntu 18.04 on CNshttps://redmine.dataone.org/issues/87822019-03-22T18:12:12ZJing Taotao@nceas.ucsb.eduMember Nodes - Story #8683 (New): USGS SDC: redeploy as a v2 Slender Node with GMNhttps://redmine.dataone.org/issues/86832018-08-22T16:25:08ZAmy Forresteraforres4@utk.eduTesting MN Management - Story #8463 (New): test: Testing & Developmenthttps://redmine.dataone.org/issues/84632018-03-01T21:04:41ZAmy Forresteraforres4@utk.edu
<p>Install or develop a functional member node to be registered to a non-production environment. </p>
Infrastructure - Story #8368 (New): Update backup strategy for jenkins job configurations to subv...https://redmine.dataone.org/issues/83682018-02-15T17:37:09ZDave Vieglaisdave.vieglais@gmail.comTesting MN Management - Story #8347 (New): Testing & Developmenthttps://redmine.dataone.org/issues/83472018-02-08T15:28:11ZMonica Ihliemail@monicaihli.com
<p>Install or develop a functional member node to be registered to a non-production environment. </p>
Member Nodes - Story #8244 (New): Upgrade Member Node to current version of Metacat (IOE)https://redmine.dataone.org/issues/82442018-01-22T16:38:20ZDave Vieglaisdave.vieglais@gmail.com
<p>The MN operations have been placed in the care of Todd Kipfer. He has requested some assistance with use of Metacat, and especially bringing it to the latest version.</p>
Infrastructure - Story #8234 (New): Use University of Kansas ORCID membership to support authenti...https://redmine.dataone.org/issues/82342018-01-09T02:00:28ZDave Vieglaisdave.vieglais@gmail.com
<p><a href="https://orcid.org/members/001G000001CAkZgIAL-university-of-kansas" class="external">KU is a premium ORCID member</a> as a member of the Greater Western Library Alliance (GWLA). As a result, KU has access to five ORCID API keys. One is currently in use for the KU DSpace instance.</p>
<p>Goal of this story is to leverage on of the remaining API keys to support ORCID authentication in the DataONE production environment.</p>
Infrastructure - Story #8036 (New): synchronization should respond to various MN down conditions ...https://redmine.dataone.org/issues/80362017-03-03T17:30:35ZRob Nahfrnahf@epscor.unm.edu
<p>Currently, synchronization <em>does</em> heed the Node.status='DOWN' in harvesting, but this is limited, especially when there are long delays between harvest and processing. tDAR uses HTTP 502 / 503 responses (not sure which) to signal that the node is temporarily down, for example. Also, for network segregation events, where a node cannot even be reached, synchronization should halt processing - the member node cannot even be notified of sync failures in these situations. </p>
<p>Thoughts on implementation would be adding Observer pattern to libclient (and/or NodeComms in synchronization) so the task can be tried again at a later time. Also try to read the Retry-After header with 503 responses.</p>
Infrastructure - Story #7889 (New): Synchronization not happening when authoritativeMN is not set...https://redmine.dataone.org/issues/78892016-09-13T17:19:40ZRob Nahfrnahf@epscor.unm.edu
<p>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).</p>
Infrastructure - Story #7183 (New): Update wild card server certificate on all test.dataone.org s...https://redmine.dataone.org/issues/71832015-06-15T14:54:13ZDave Vieglaisdave.vieglais@gmail.com
<p>The *.test.dataone.org server certificate expires in July.</p>
<p>A replacement has been ordered and will be stored in subversion:</p>
<p>AdminAccounts.txt</p>
<p>The servers impacted are listed on the Google Sheet:</p>
<p><a href="https://docs.google.com/spreadsheets/d/1BrZgm0yPV9dzd6SIfjQ9P5W5WH666xaGAI6KeXTAiFs/edit#gid=0">https://docs.google.com/spreadsheets/d/1BrZgm0yPV9dzd6SIfjQ9P5W5WH666xaGAI6KeXTAiFs/edit#gid=0</a></p>
Python GMN - Story #7095 (New): Support HTTP redirect capability for GMN within the Vendor Specif...https://redmine.dataone.org/issues/70952015-05-12T16:20:39ZMark Servillamark.servilla@gmail.com
<p>GMN provides proxy capabilities to integrate existing content residing in a back-end data repository through its Vendor Specific Extension model. Only minimal support exists within the GMN-VSE model for HTTP redirects. Although the use of HTTP redirects is more of an exception within the the GMN-VSE model, it can provide a flexible mechanism for MNs who dynamically manage data and metadata objects.</p>
Infrastructure - Story #6883 (New): support for ESRI Shapefile object formathttps://redmine.dataone.org/issues/68832015-03-11T01:53:35ZMatthew Jonesjones@nceas.ucsb.edu
<p>We are missing shapefiles from the format list, and need to add them as a data type. The identifier of a shapefile is unclear, but here is the entry from UDFR:</p>
<p><a href="http://udfr.org/ontowiki/view/r/u1f590">http://udfr.org/ontowiki/view/r/u1f590</a></p>
<p>Also see details:</p>
<p><a href="http://en.wikipedia.org/wiki/Shapefile">http://en.wikipedia.org/wiki/Shapefile</a></p>
Infrastructure - Story #6543 (New): Support RIF-CS metadata standardhttps://redmine.dataone.org/issues/65432014-11-03T00:23:31ZBruce Wilsonbwilso27@utk.edu
<p>Broadly used in the australian ecoinformatics community. URL is <a href="http://www.ands.org.au/resource/rif-cs.html">http://www.ands.org.au/resource/rif-cs.html</a>. AEKOS is planning to work with EML initially, but RIF-CS is their native format. </p>