Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Services can't be deployed. AWSSBInjectedGetCidrs and AWSSBInjectedGetAzs custom resources just hang. #251

Open
alekskarmyzov opened this issue Nov 20, 2021 · 1 comment

Comments

@alekskarmyzov
Copy link

Describe the bug
I am trying to deploy any service via AWS service broker (I've tried a Kubernetes and Tanzu Application Service, result is the same).
CloudFormation stack goes fine until the creation of two custom resources: AWSSBInjectedGetCidrs and AWSSBInjectedGetAzs.
Then they just hang for a very long time until the timeout error.

To Reproduce
Try to deploy any service via AWS service broker.

Expected behavior
Service is successfully deployed by AWS service broker.

Screenshots
image

Environment (please complete the following information):

  • Application Platform: Tanzu Application Service, Kubernetes
  • Application Platform Version: TAS v2.12.1, Kubernetes v1.21
  • Broker Version: 1.0.4
@AnilReddy231
Copy link

Hello @alekskarmyzov ,

Cloudformation will wait for Custom Resource lambdas to respond with cfnresponse.status_code. I am guessing, your lambda is failing for some reason and unable to send status back to CFN stack. I would suggest to look into error logs in cloudwatch log streams for these lambda's. Make sure that role which is being used to run custom lambda's has appropriate IAM permission to log into cloudwatch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants