StateMachine PipelineDeletionStateMachine is in failed

[americanjohnny1988]

StateMachine PipelineDeletionStateMachine is in failed

[sbkok]

Thank you for reporting this issue and taking the time to investigate in a call.

The issue was caused by stale deployment pipeline region SSM parameters.
With the fixes introduced in #535 and released as part of v3.2.0, these get deleted after deleting the CloudFormation stack. Before v3.2.0, there was a bug that did not effectively delete the SSM parameters.
Regarding the issue above, these stale SSM parameters were left behind and went undetected until yesterday.

For others that run into a similar issue, this is how you can check:

1. In the deployment account, main deployment region, navigate to the PipelineDeletionStateMachine in AWS Step Functions, open the last execution.
2. Look at which ADF pipelines failed to perform the CloudFormation Delete Stack operation.
3. For each of the failed pipelines, check if the CloudFormation stack exists, named adf-pipeline-${pipeline-name-goes-here}.
4. If the stack exists, stop here and report a new issue.
5. If the stack does not exist, while it attempts to delete it, go to AWS Systems Manager.
6. Go to Parameter Store.
7. Filter the parameters, search for /deployment/S3/${pipeline-name-goes-here}/regions. Please note, pipeline-name-goes-here does not start with adf-pipeline-. Use the name that follows that prefix.
8. Delete the SSM Parameter.
9. Trigger a new change in the AWS CodePipeline named aws-deployment-framework-pipelines.

The issue was resolved using the steps listed above.