Bug #6780
mn.create to metacat (mn-demo-6) failing with schema validation error
100%
Description
When running existing API tests against mn-demo-6.test.dataone.org/knb/d1/mn, we get a schema validation error that looks to be due to a server-side misconfiguration, rather than malformed data coming from the client. (These tests used to pass, many months ago).
We need a well-configured v1 MN in order to validate the refactored tests.
The error:
Error inserting or updating document: <?xml version="1.0"?>schema_reference.4: Failed to read schema document 'https://mn-demo-6.test.dataone.org:443/knb/schema/eml-2.0.1/eml.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. [for host POST https://mn-demo-6.test.dataone.org/knb/d1/mn/v1/object; MMP message has: ParamPart:pid = TierTesting:mn-demo-6:Verified_READ.14; FilePart:object = /tmp/mmp.output.7996860562999152203.tmp (17181 bytes); FilePart:sysmeta = /tmp/mmp.output.1555642702138371339.tmp (804 bytes); ]
the eml document used for the create starts with:
<?xml version="1.0" encoding="UTF-8"?>
PISCO moored temperature, TPT001
PISCO: Physical Oceanography: moored temperature data: Terrace Point, California, USA (TPT001)
and the full document is attached.
History
#1 Updated by Jing Tao over 9 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Just confirmed that the error had gone. Close the bug.