Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2]

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2]


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Joe Breen <>, "" <>
  • Subject: Re: [perfsonar-user] Unable to determine the lead participant: At /schema: 1 is not one of [2]
  • Date: Thu, 25 Jun 2020 14:05:52 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=A09ZIeLPDtychytlCy+vdGGvaw0hba9oNd+ZrvSN8Ys=; b=B3XbN3hfzve7SrrnL0YZsKFhz6FIwNvU/SS0pHZzHGS/4Jcd8IswXSeGpemW3X1AgqqqT3S2LVgomnGAt1jl6dWEdYivor428fvO7BiNrEGxX/n1FeWKwU4iCBtDyYgrw1GrVfRpUHQfof3as0tAUxx/06gT1vwe53C3V++IBYn7HYmAQUvkJe/E6st39nMrBR/m8JysFj0jxFxDJ7dVNwC4UE52WxDpZX+jgV0vDHDnxbUUT7WTMV0kqW2dCvkL8Hh6sAsAUYj/NE4ufTP8Gzn5C5Zhv2y9tEFdlqjCrP0xM48eXITpu/U9NsEyGGyKV/t2Vhs9t9GAU6GMTcKLTA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oEH5elRzaFx/QdMpmFa9YbbO/ud5T22Kjn4Mqg34luuan/TYXA8ByZa+dJPcTGkA1zSL2Gzr7JZvOfCr3OEgit7e4uNsU+OhYKzKa+QtMhMQaKamj8VvgUEYmY/OyFY7bIVggjxV4hDaVRWpjdZs282vEpKohx+yu4mMNSOOpHCHEn3oYSgH6C8KX0vRm/aSi0pxUv7zR9MUyuHzxoiUFUKVPUsLjQhc5D6+Ks3p/pIQOd9rhwlhMT+j5dBDZESc84BElU8OHIHNA6ytcDlH7kDuorbJOGoGTBfpMCjkQEMQgI03tBRemSAsfkchEjqSZKCvmzMesQJ9HfMFO613NA==

Joe Breen writes:

 

##############

[chpcadmin@uofu-science-dmz-bandwidth ~]$ pscheduler task throughput --source uofu-ddc-dmz-latency.chpc.utah.edu
Submitting task...
Unable to determine the lead participant: At /schema: 1 is not one of [2]

##############

 

If I swap --source for --dest for the same address, I receive results.  If I explicitly put in the --dest and --source, I receive results:

 

The destination is a required parameter.  The error message is dreadfully bad thanks to the library that parses the JSON schemas for the test specifications.  That’s been remedied in 4.3:

 

$ pscheduler task throughput --source foo.bar.org

Submitting task...

Unable to determine the lead participant: At /: 'dest' is a required property

 

Slightly more detail here:  https://github.com/perfsonar/pscheduler/issues/979.  Issue 427 was a side effect of the BWCTL backward-compatibility code that we nuked from orbit in 4.2.

 

--Mark

 


Archive powered by MHonArc 2.6.19.

Top of Page