| Description |
This article describes the API URL error 404 resource not found if FortiGate GCP HA uses multiple SDN connectors. |
| Scope | FortiGate GCP VM. |
| Solution |
When setting up FortiGate HA SDN in the GCP environment, if the resources are in different projects, it will show the below errors:
get instance nic: nic3, *.*.*.*, interface, accessConfig(External NAT), eip(*.*.*.*), tier (PREMIUM) gcpd checking eip: fgfw1-untrust eip: fgfw1-untrust (*.*.*.*) attached instance: *********, zone: ******** eip ******* is attached in local instance already gcpd checking route: route gcpd api result: 484 { "error": { "code": 404, "message": "The resource 'projects/********/global/routes/route' was not found", "errors": [ { "message": "The resource projects/*****/global/routes/ route' was not found", "domain": "global", "reason": "notFound" api url: https://www.googleapis.com/compute/v1/projects/****/global/routes/route "error": { { "code": 404, "message": "The resource projects/****/global/routes/route' was not found", "errors": [ { "message": "The resource projects/******/global/routes/ route' was not found", "domain": "global", "reason": "notFound" Getting route info failed: route, skip failover. GCP guest envirot update GCP update done
The routing table was not found as it was in the second resource project. When putting two project IDs in the list, API only replies with the first project. Multiple project IDs in the connector config are only for pulling metadata for dynamic objects, not for fail-over.
It is necessary to put all resources in the same project or use FortiGate-VM HA with external and internal LB. |
