Running jobs shows as failed in API until done.

R

RealSoulskater

Member
Aug 21, 2022
9
0
21
Hi

I'm currently running a dashboard called Homepage where i have a widget that checks for disk space and failed Tasks 24h back.

It calls the API like this where since is set dynamically to check 24H back:

Code: 
/api2/json/nodes/localhost/tasks?limit=100&errors=true&since=1787658006

The problem is that running tasks shows up as failed until they are done and if successfully completed they go away.

What i have seen when manually testing directly against the API is that running tasks has no status key at all.

Running job:
JSON: 
{
      "upid": "e304958304598:",
      "node": "localhost",
      "pid": 1337,
      "pstart": 1710,
      "starttime": 1787741689,
      "worker_type": "verificationjob",
      "worker_id": "mybackup01:v-07936a91-9de4",
      "user": "xxx"
    }

While other jobs have.

Other:
JSON: 
{
      "upid": "wpeoriweproiwerpoiu:",
      "node": "localhost",
      "pid": 440913,
      "pstart": 823190969,
      "starttime": 1745192750,
      "worker_type": "aptupdate",
      "worker_id": null,
      "user": "xxx",
      "endtime": 1745192750,
      "status": "unknown"
    }

{
      "upid": "erpoti348907weriuy:",
      "node": "localhost",
      "pid": 1337,
      "pstart": 1710,
      "starttime": 1787742000,
      "worker_type": "prunejob",
      "worker_id": "mybackup01",
      "user": "xxx",
      "endtime": 1787742000,
      "status": "OK"
    }

    {
      "upid": "UPID:xxx:rte098345iuretoiu345098:aptupdate::xxx:",
      "node": "localhost",
      "pid": 1622,
      "pstart": 5832,
      "starttime": 1782836076,
      "worker_type": "aptupdate",
      "worker_id": null,
      "user": "xxx",
      "endtime": 1782836077,
      "status": "WARNINGS: 1"
    }

I have seen in my testing also that errors=true only removes the OK ones, unknown and warnings for example still shows up.

Testing against this /api2/json/nodes/localhost/tasks?limit=100&errors=true should only yield errors but does not.

I'm running the latest version 4.2.5.

There are no errors when the API call is run so nothing seems to be wrong in the API call itself.

Is this an intended behavior or a bug perhaps?

/Regards
Marcus
 
For reference:
A

Thread 'PBS API show running task as erroneous'

Hello!
The topic says it by itself. I have configured monitoring for failed task via API, and i got a little confused with results i got. It is not a big issue, anyway, because template is checking for an endtime value.
Here are responses with different filters

Here is everything totally OK, as i expected, two running tasks, total is 2
Code: 
curl -k -X GET 'https://PBS:8007/api2/json/nodes/0/tasks?running=true' -H 'Authorization: PBSAPIToken=xxxxxxxxx' | jq
{
"total": 2,
"data": [
{
"upid": "UPID:PBS:00000278:000003BA:00000322:67DBA0D0:syncjob",
"node"...
https://bugzilla.proxmox.com/show_bug.cgi?id=6251
 
Ok, so there is a bug report on this, sadly it is over a year old and still in state new and it reference another bug sitting at undecided, also for over a year...

Bug reports: 6251 & 6571

From 6571:
those parameters don't mean what you think they mean:

errors => "Only list erroneous tasks."
running => "Only list running tasks."

the inverse of "Only list running tasks." is "Do not only list running tasks.", not "Only list finished tasks." (same for "errors").

we could probably add additional filters, or revamp the filtering system altogether, to allow your desired semantics.
Click to expand...

So it might not be possible to get desired status at the moment, i hope they pick up on this soon and fix.
 
You must log in or register to reply here.
Top Bottom
Back