fortinet / fortigate-autoscale Goto Github PK

This appears to be a bug in v1.0.3 and v1.0.4 (not v1.0.2)

When deploying to AWS using Cloudformation, this error occurs:
Template error: Mapping named 'FortiGateKeyMap' is not present in the 'Mappings' section of template.

This appears to be due to an invalid reference in workload.template to 'FortiGateKeyMap', which no longer exists as of v1.0.3.

i've run cf template for aws autoscaling in ap-northeast-2 region.

but i've meet error "Not authorized image error ami-0a560b6c089c6310a"

How do i resolve this error?

deployed using the 2.0.8 "fortigate-autoscale-aws-cloudformation.zip" -

used the templates\autoscale-new-vpc.template CFT to deploy stack

Deployed this twice - both times in US-EAST-2 AZ A, and AZ B.

in the first deployment the Masterfortigate in the autoscale group did not deploy with the 2nd ENI - connected to private 1 subnet.
it only deployed with public 1 subnet eni. -- the non master (set my desired instances to 2) did indeed deploy with 2 ENI, public 2, and private 2 networks.

Scale out did work correctly - scaled out fortigate did include 2 eni (public and private)

deleted the stack and deployed again to determine if problem could be recreated.

in my second deployment BOTH fortigates only had single eni in public 1 and public 2 subnet.

Deleted and went back to using 2.0.7 which functioned normally.

Information about deployement:
t2.small type (basic proof of concept deployment)
PAYG instance types

hi there,

when i deployed stage 2 template, an error pop up saying:

The template deployment failed with error: 'The resource with id: '/subscriptions/13ce02fc-b6d8-40f6-8d67-bb402bd8482f/resourceGroups/tc-gateway/providers/Microsoft.Compute/virtualMachineScaleSets/tcpayg' failed validation with message: 'The requested size for resource '/subscriptions/13ce02fc-b6d8-40f6-8d67-bb402bd8482f/resourceGroups/tc-gateway/providers/Microsoft.Compute/virtualMachineScaleSets/tcpayg' is currently not available in location 'australiaeast' zones '' for subscription '13ce02fc-b6d8-40f6-8d67-bb402bd8482f'. Please try another size or deploy to a different location or zones. See https://aka.ms/azureskunotavailable for details.'.'. (Code: InvalidTemplateDeployment)

i have check my Azure SKU and changed the VM size to the supported size and still getting the same error.

can you please advise

This is a known issue introduced in 2.0.1. Please do not use this button until it's fixed.
Follow the instructions in the official documentation to deploy.

Just tried to deploy the new 2.0.2 template but stack deployment failed with these errors:

The following resource(s) failed to create: [FgtAsgVpcEndpoint].
FgtAsgVpcEndpoint | CREATE_FAILED | VPC Endpoint vpce-0d6a14c4f005210e4 did not stabilize.

In the latest version. Azure Function defaults to use a non-existing package zip file from 1.0.0-alpha.2; see below:
"packageResUrl": { "type": "string", "defaultValue": "https://github.com/fortinet/fortigate-autoscale/releases/download/1.0.0-alpha.2/fortigate-autoscale-azure-funcapp.zip", "metadata": { "description": "The public URL of package zip which contains the resource used to deploy the Function App." } }

issue is found in:
fortigate-autoscale/azure_quickstart/templates/deploy_funcapp.json

This template is failing to deploy due to nodejs8.10 being EOL. We tried updating the runtime references to nodejs12.x but the deployment still fails when creating resources. One of the errors was "Cannot find module 'uuid/v5'". It looks like some modules are missing from the zip files.

The following issues have been observed in the fortigate-autoscale v1.0.4 (Latest Release). 

temporary workaround as follows :
In file deploy_scaleset.json, line 460: replace the whole line

"name": "fortinet_fg-vm_payg",

with

"name": "fortinet_fg-vm_payg_20190624",

As soon as this was modified, it completed fine.

This bug will be fixed in a following release.

This is occuring on v1.0.2 of the code as v1.0.3 and v1.0.4 have an unrelated issue that blocks deployment.

When deploying the CFN template, the 'StackDeployFgtAsgSolution' nested template fails with the error:
API: ec2:RunInstances Not authorized for images: [ami-09e4f25ec992c94ab]

This appears to be occuring in the file create-fortigate.template