Closed okraskaj closed 3 years ago
It is worth noting that the referenced job -> `6d37ccb1-0a71-4e95-b579-fff0126e8229 didn't exist because during development there was an exception before submitting the POST call to Kubernetes API.
But in any case, since this could happen, that a job(s) associated with the workflow, for some reason, don't get created, stop
should give a user understandable error and stop --force
should just work.
Duplicate of https://github.com/reanahub/reana-client/issues/360.
It fails in reana-job-controller because there is no job to be deleted.
We should just delete everything connected with job regardless of what is running and what is not.