Remove "running" WFs from Admin UI (after having killed their jobs)

[ypatios ypatios]

Hello everyone,

let's assume someone is reckless enough to remove some running jobs from the service registry using DELETE service/job/{id}. (Operation:"START_OPERATION"; Type:"org.opencastproject.workflow")

How could they then remove the respective workflow instances in the Admin UI (which still appear with state "running" but are actually hollow)?

Asking for a friend of course.

Thank you,

ypatios

ps: I have tried various api ways that I thought appropriate; I have also cleared and recreated the Admin UI index: neither solved the problem.

[Greg Logan]

Hi ypatios,

Have you tried the /workflow/stop REST endpoint?

G

--
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.

[ypatios ypatios]

Hello Greg,

I did, but if I understand correctly, stopping a workflow does the following:

– waits for current running operation to finish

– cancels start of next operation (and thus stops the wf).

So, when I tried this I had no luck as the running operation never finishes.

In the Event Details/Workflows I can see the status Stopped, but the affected operation still appears as running.

Thanks,

ypatios

To unsubscribe from this group and stop receiving emails from it, send an email to us...@opencast.org.

[Greg Logan]

Hi ypatios,

Hrm, so the workflow itself is likely stopped, but there are stuck jobs.  If you've got the job ids, can you use DELETE /services/job/{id} endpoint to remove them?  If there are multiple you could also use POST /services/removejobs with the jobIds field.

G

To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.

[ypatios ypatios]

Hello Greg,

Hrm, so the workflow itself is likely stopped, but there are stuck jobs.  If you've got the job ids, can you use DELETE /services/job/{id} endpoint to remove them?  If there are multiple you could also use POST /services/removejobs with the jobIds field.

this is exactly that caused the problem in the first place x_D

But your suggestion brought me back to the REST docs where I started trying things out again...

We installed a server update the other day and we had to restart Opencast and we also rebuilt the admin-UI AssetManager index. It seems that that helped, as now the following did work:

DELETE /api/workflows/{workflowInstanceId}

...which did not work when I first tried it (right after the incident).

So, the stuck workflows (stopped but with running operations) are now gone.

Thanks!

ypatios

[gregor]

Can you please explain in detail how you use the REST DELETE

[Greg Logan]

Hi Gregor,

You can use the REST docs.  The specific endpoint in question is https://stable.opencast.org/docs.html?path=/api/workflows#deleteworkflowinstance-2.

G