Yorc can't undeploy a stucked deployment on K8S

[adidanes]

Bug Report

Description

In case a deployment on a K8S location stucks, for example the deployment rests in status DEPLOYMENT_IN_PROGRESS (in the K8S console pods are pending), the undeploy fails with erreor "400 Bad Request"

Expected behavior

Should be able to force an undeploy.

Actual behavior

We have a Yorc deployment on K8S that stucks in DEPLOYMENT_IN_PROGRESS with one Node in creating status and a Deploy task in RUNNING status.
The undeply command fails with Error: Bad Request: "Task witth <TASK_ID> and status RUNNING already exists for target <DEPLOYMENT_ID>

Steps to reproduce the issue

Deploy a Yorc stack with Yorc. If the ConfigMap volume is not correctly configured in the A4C location, the deployment will stuck. The ConfigMap volume must have set the spec.name property to the name of the K8S ConfigMap's name.

Output of yorc version

4.0.0

Yorc configuration file

Priority

Medium

• High = We should stop anything we are doing and do this. If you're writing this calmly, you should probably choose another option. If it's really that urgent, please make sure we read this.
• Medium = It's important that we do this within a few days.
• Low = We will consider this on our next sprint planning.

(Please be aware that your priority may not match ours, we'll use this as guidance only).