Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS test presents different behaviour under Ubuntu and Debian #1493

Open
szymontrocha opened this issue Dec 11, 2024 · 1 comment
Open

DNS test presents different behaviour under Ubuntu and Debian #1493

szymontrocha opened this issue Dec 11, 2024 · 1 comment
Assignees
Labels

Comments

@szymontrocha
Copy link

I observed it in a fresh toolkit installations:

(Debian 12 host)

# pscheduler task http --url=www.pcss.pl
Submitting task...
Unable to determine the lead participant: At /url: 'www.pcss.pl' is not a 'uri'

(Ubuntu 20 host)

$ pscheduler task http --url=www.pcss.pl
Submitting task...
Task URL:
https://perfsonar2/pscheduler/tasks/766703c8-e542-41c0-9d64-50c8f9833834
Running with tool 'curl'
Fetching first run...

Next scheduled run:
https://perfsonar2/pscheduler/tasks/766703c8-e542-41c0-9d64-50c8f9833834/runs/2972fd9e-c36f-40a7-9938-c636bf399502
Starts 2024-12-10T18:29:13+00:00 (~1 seconds)
Ends   2024-12-10T18:29:23+00:00 (~9 seconds)
Waiting for result...

Response Time ... PT2.519671S
Status Code ..... Not Specified

No further runs scheduled.

Questions follow:

  • Is http(s) prefix strictly required in task command?
  • If yes it shouldn't work in both OSes equally and we need to write it in the docs. Currently docs (or --help) don't specify it
@mfeit-internet2
Copy link
Member

mfeit-internet2 commented Dec 11, 2024

I investigated this on EL and found the same behavior.

The pScheduler code doesn't vary between distributions and parses URLs as strings with JSON Schema's uri modifier. This may indicate a difference in libraries between distributions. Investigate upgrading JSON Schema everywhere so this works properly.

@arlake228 arlake228 self-assigned this Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Ready
Development

No branches or pull requests

3 participants