Closed JeffGiroux closed 1 year ago
To workaround this...simply create a GTM server object with the name that you specify in parameter 'deploymentName'. If the GTM server object is created first, then template will work.
"deploymentName": {
"Default": "example",
"Description": "Name the template uses to create object names",
"MaxLength": 25,
"Type": "String"
},
Thanks for pointing this out and for also providing a detailed workaround. We will take a look at this and are now tracking it with internal ID ESECLDTPLT-3068.
Closing due to age. These legacy templates are now in maintenance mode and are being replaced by our next-generation templates available in the Cloud Templates 2.0 GitHub repo.
Testing DNS scaling with customer and trying the autoscale-via-dns template.
https://github.com/F5Networks/f5-aws-cloudformation/tree/main/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg
When the BIG-IP device tries to list existing GTM server objects as well as create itself as a GTM server object, fail. If you manually create the GTM server object first, then the template is successful and the BIG-IP device successfully adds itself to the GTM.
bigip box error...
The README states a few pre-reqs. However, it does not mention that the server object MUST be created first too. If this is not the case, then the cloudlibs script need to be updated as that is where the error seems to happen. I noticed that doing a list and create on the server objects is throwing error.
gtm box error...