In some edge situations (due failure with Ansible, machine crash, etc.), the database may present an inconsistent state where the last deployment state stays RUNNING while no Ansible task are running. However, only deployment with a FAILURE state can be resumed using the tdp plan resume command.
We should add an option/command/sub-command to recover from this state. It should allow to:
- Update the last deployment state from
RUNNING to FAILURE
- Update the operations:
- If an operation is
RUNNING, update it to FAILURE and set the following operations to HELD
- If an operation is
PENDING or HELD, update it to HELD and set the following operations to HELD
In some edge situations (due failure with Ansible, machine crash, etc.), the database may present an inconsistent state where the last deployment state stays
RUNNINGwhile no Ansible task are running. However, only deployment with aFAILUREstate can be resumed using thetdp plan resumecommand.We should add an option/command/sub-command to recover from this state. It should allow to:
RUNNINGtoFAILURERUNNING, update it toFAILUREand set the following operations toHELDPENDINGorHELD, update it toHELDand set the following operations toHELD