aws-cloudformation / aws-cloudformation/cloudformation-cli

cfn submit fails with opaque `Internal Failure`

Open
#875 7 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
336
Forks
172
Avg merge
3d 5m
Merged PRs (30d)
3

Description

[rpdk.log](https://github.com/aws-cloudformation/cloudformation-cli/files/8385001/rpdk.log) is attached.

I'm registering a custom resource type in multiple AWS accounts using the [typescript plugin](https://github.com/aws-cloudformation/cloudformation-cli-typescript-plugin). I've had success in most accounts and am already using the custom resource in a few stacks. But in a particular account, `cfn submit` always fails while waiting for registration to complete:

```
Successfully submitted type. Waiting for registration with token 'c372ede9-e066-4d70-9cdd-6894c7a1e715' to complete.
Failed to register the type with registration token 'c372ede9-e066-4d70-9cdd-6894c7a1e715'.
Please see response for additional information: '{'ProgressStatus': 'FAILED', 'Description': 'Deployment is currently in DEPLOY_STAGE of status FAILED\nDeployment failed with error. Error message: [c372ede9-e066-4d70-9cdd-6894c7a1e715] Internal Failure', 'TypeArn': 'arn:aws:cloudformation:us-east-1:135761614524:type/resource/Extend-Confluent-RoleBinding', 'TypeVersionArn': 'arn:aws:cloudformation:us-east-1:135761614524:type/resource/Extend-Confluent-RoleBinding/00000001', 'ResponseMetadata': {'RequestId': '38daa4e7-90bd-4192-b5b9-a569cf402b70', 'HTTPStatusCode': 200, 'HTTPHeaders': {'x-amzn-requestid': '38daa4e7-90bd-4192-b5b9-a569cf402b70', 'content-type': 'text/xml', 'content-length': '789', 'date': 'Thu, 31 Mar 2022 00:32:16 GMT'}, 'RetryAttempts': 0}}'
=== Caught downstream error ===
Waiter TypeRegistrationComplete failed: Waiter encountered a terminal failure state: For expression "ProgressStatus" we matched expected path: "FAILED"
```

I've retried multiple times, tried deleting and recreating `CloudFormationManagedUploadInfrastructure`, with no luck. I've confirmed that I can submit other resource types to this account without issue, and I can submit this resource type to other accounts without issue. The error message is always the same, aside from a different registration token each time.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.