action #96510
Updated by okurz over 1 year ago
## Observation
from api documentation
~~~
DELETE +/job_groups/<group_id:num> Deletes a job group. Verifies that it is not empty before attempting to remove
~~~
with yaml definition of job_groups isn't possible to have empty job_group, so verification always stops call with error 400
~~~ text
openqa-cli api --osd -X DELETE job_groups/390
400 Bad Request
{"error":"Job group 390 is not empty","error_status":400}
~~~
empty template contains `"products: {}\nscenarios: {}\"` string ...
## Workaround
* Alternative 1: Delete job group over database SQL commands
* Alternative 2: To be confirmed: Empty the template document before trying to delete the job group
from api documentation
~~~
DELETE +/job_groups/<group_id:num> Deletes a job group. Verifies that it is not empty before attempting to remove
~~~
with yaml definition of job_groups isn't possible to have empty job_group, so verification always stops call with error 400
~~~ text
openqa-cli api --osd -X DELETE job_groups/390
400 Bad Request
{"error":"Job group 390 is not empty","error_status":400}
~~~
empty template contains `"products: {}\nscenarios: {}\"` string ...
## Workaround
* Alternative 1: Delete job group over database SQL commands
* Alternative 2: To be confirmed: Empty the template document before trying to delete the job group