Skip to Content.
Sympa Menu

perfsonar-user - Re: Re: Re: [perfsonar-user] "Task forbidden by limits", maybe an IPV6 problem?

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: Re: Re: [perfsonar-user] "Task forbidden by limits", maybe an IPV6 problem?


Chronological Thread 
  • From:
  • To:
  • Subject: Re: Re: Re: [perfsonar-user] "Task forbidden by limits", maybe an IPV6 problem?
  • Date: Wed, 3 Oct 2018 19:48:41 +0000 (UTC)
  • Ironport-phdr: 9a23:C2uaQBOhob3W450PmOsl6mtUPXoX/o7sNwtQ0KIMzox0LPv+rarrMEGX3/hxlliBBdydt6obzbKO+4nbGkU4qa6bt34DdJEeHzQksu4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2aFLduGC94iAPERvjKwV1Ov71GonPhMiryuy+4ZLebxlKiTanfb9+MAi9oBnMuMURnYZsMLs6xAHTontPdeRWxGdoKkyWkh3h+Mq+/4Nt/jpJtf45+MFOTav1f6IjTbxFFzsmKHw65NfqtRbYUwSC4GYXX3gMnRpJBwjF6wz6Xov0vyDnuOdxxDWWMMvrRr0yRD+s7bpkSAXwhSkZNzA37WPYhM9/g61HrxyvoBJxzpXIYI+ILvdyYrnQcc8ESWdHQ81fVzZBAoS5b4YXF+oOI+dYr5PhqFQQtha+ABOjBOLpyjBWnHP5w7A10/knHArb3wIgB8oDvGrIoNj3LqsfU+C4wLPVwTjCYP5awynx5JbVfh0nvPqCR6h/cdDLxkkqDw7FjkufqYjiPz6N0uQNsnOb7/Z7Ve6xkWInqgdxoiSxycc2jInGmJ4Vxk7e+Spn3Yk1OMW0SE99YdG6DJtdrz+WO5d0T884QWxluDw2xqAHtJO0ZiQG1oorywPHZ/yCaYeI4xbjVOiLITd/gXJoYKq/hwup/ki7yuz8U9G030xRoypElNnMqm4C1wbV6seZVvtx4F2t1iiS2ADO8u1EO1w7lbLHK549xb49joITvlrZHi/4g0X2i6mWeV8++uSx9uTneavppoWHOo9wiwH+KbgumtehDegiMwgOWXSb9vqm1L3l40L5XKtGguconabErZCJbfgc87a0GQFO1YAq8VOiFDq8+NUegXQdKl9ZIlSKg5W6FUvJJaXgAPaliFmElT5qwf2AM7H8UcaFFWTKjLq0JeU10EVb0gdmld0=

Continuing to look at this, my task is classified as both 'default' &
'friendlies'.

The Application section indicates the test should PASS the 'friendlies'
section and run the test. However is seems it continues on to check the
'default' section which includes a stop-on-failure which makes it FAIL. Seems
like a logic bug in the Applications section or am I understanding this
incorrectly? It says it should be sequential, "until one passes" and that
does not seem to be happening.

Removing the "stop-on-failure" directive in the 'default' section allows this
test to run.
I also re-added the r-and-e ' ip-cidr-list-url identifier as that seems
helpful to have available.


"#":
"-------------------------------------------------------------------",
"#": "APPLICATIONS: TO WHOM DO WE APPLY THE LIMITS?
",
"#": "
",
"#": "These are processed in order until one passes all of the
",
"#": "requirements. The run will be rejected if one fails with
",
"#": "stop-on-failure set to true or none of them passes.
",
"#":
"-------------------------------------------------------------------",

"applications": [
{
"description": "Hosts we don't want running any tests",
"classifier": "hostiles",
"apply": [
{ "require": "all", "limits": [ "never" ] }
],
"stop-on-failure": true
},
{
"description": "Hosts we trust to do everything",
"classifier": "friendlies",
"apply": [
{ "require": "all", "limits": [ "always" ] }
]
},
{
"description": "Defaults applied to non-friendly hosts",
"classifier": "default",
"apply": [
{ "require": "any", "limits": [ "never" ] }
],
"stop-on-failure": true
}
]



$ sudo pscheduler task rtt --dest 127.0.0.1
Submitting task...
Unable to post task: Task forbidden by limits:
Hints:
requester: ::1
server: ::1
Identified as everybody, local-interfaces
Classified as default, friendlies
Application: Hosts we trust to do everything
Group 1: Limit 'always' passed
Group 1: Want all, 1/1 passed, 0/1 failed: PASS
Application PASSES
Application: Defaults applied to non-friendly hosts
Group 1: Limit 'never' failed: Forced failure
Group 1: Want all, 0/1 passed, 1/1 failed: FAIL
Group 1: Failed; stopping here.
Application FAILS
Failed - Stop Forced
Proposal does not meet limits

Garry Peirce
Networkmaine, UMS



Archive powered by MHonArc 2.6.19.

Top of Page