Pipeline Fails Due to a Previous Configuration Reference about landing-zone-accelerator-on-aws HOT 2 CLOSED

I have continued to try and troubleshoot this issue by deleting the Prepare Stack and letting it get rebuilt by the pipeline. I have also confirmed that the reference to the OU in question is not listed in the DynamoDB tables that are created in the prepare stack. In addition, adding an account to the accounts-config.yaml resulted in the new account being created, and then the same failure of a reference to a non-existent component.
Any information regarding where the artifact of an account ID could be referenced by the prepare stack, CustomCreateControlTowerAccount resource could be sourced from would be helpful.

from landing-zone-accelerator-on-aws.

I was able to track this issue to a service catalog Provisioned Product that was in a error state. Terminating the failed provisioned product allowed the pipeline to continue. What made this difficult was that the error log did not indicate a problem with service catalog. It would be very useful to add the provisioned product ID to the error message in the function provisionSuccess(). The vague terms of "Provisioning failure error message" did not indicate where to look for the problem.

from landing-zone-accelerator-on-aws.