search

F5Networks / f5-aws-cloudformation-v2

AWS Cloudformation Templates for quickly deploying BIG-IP services in AWS
12 stars 21 forks source link

Unable to deploy quickstart on existing network: The following resource(s) failed to create: [Bigip3NicInstance]. #28

Closed marinalf closed 1 year ago

marinalf commented 1 year ago

Problem Description

I am using the launch stack button to deploy the "Quickstart Existing Network" CF template. I filled up all the networking information to match my external/internal/mgmt subnet as well as all the required fields, and left everything else default. It successfully creates a few constructs such as EIP, SGs, etc, but it stops here and starts rollback:

The following resource(s) failed to create: [Bigip3NicInstance].

I also tried the full stack, and same behavior, it does not go through this point. Subscription for the default image is there, along with EIP limit increased. Am I missing anything else?

Screenshots

image
f5-applebaum commented 1 year ago

Looks like it's failing at "Failed to receive 1 resource signal"

We. send a signal to Cloudformation once startup script is complete to let Cloudformation that BIG-IP is finished onboarding and ready. ex. https://github.com/F5Networks/f5-aws-cloudformation-v2/blob/main/examples/modules/bigip-standalone/bigip-standalone.yaml#L1198-L1201

If Cloudformation is NOT receiving that signal, it means startup script is failing to get to that point. Do the BIG-IPs have access to the Internet in order to download the required files ( runtime-init package and config file)? Are there any special restrictions in your environment, ex. DNS, routing, etc. that could affect that. The only way to discover/troubleshoot this is to SSH into the instance and check the logs to see what is going on:

From: Troubleshooting Section: https://github.com/F5Networks/f5-aws-cloudformation-v2/tree/main/examples/quickstart#troubleshooting-steps

/var/log/cloud/startup-script.log /var/log/cloud/bigIpRuntimeInit.log

You might also be able to see where the errors are via the Console log as the scripts should log to that as well?

marinalf commented 1 year ago

I am using custom SGs for internal/external/mgmt access, and the external SG did not have outbound rule to download the required files. It is all good now. Thank you!

shyawnkarim commented 1 year ago

Closing.

Please open another issue if you would like additional assistance.