Known issues
Known issues are organized into the following categories:
To inquire about a particular bug or to report a bug, please contact Fortinet Customer Service & Support.
New known issues
The following issues have been identified in version 8.0.0.
Others
|
Bug ID |
Description |
|---|---|
|
1283931 |
When FortiManager operates in Workflow mode, changes to the global ADOM database may not be reflected in local ADOMs after assigning a Global Policy Package. A session is created; however, the View Diff function returns “No Difference.” |
Policy and Objects
|
Bug ID |
Description |
|---|---|
|
1282087 |
FortiManager for each policy Installation consistently pushes "config endpoint-control fctems" to configure out-of-sync-threshold 180. While this does not cause an installation failure, the change is reapplied during every install operation. |
Existing known issues
The following issues have been identified in a previous version of FortiManager and remain in FortiManager 8.0.0.
AP Manager
|
Bug ID |
Description |
|---|---|
|
1263157 |
FortiManager may become unresponsive when upgrading FortiSwitch or FortiAP using a Firmware Template. |
Device Manager
|
Bug ID |
Description |
|---|---|
|
980362 |
The Firmware Version column in Device Manager incorrectly shows "Upgrading FortiGate from V1 to V2" even after a successful upgrade has been completed. |
|
1136726 |
Enabling the Power Supply Failure option in an SNMP v2 configuration applied via a System Template results in the following installation error: multi-option(power-blade-down) not exist". |
|
1212747 |
Certificate generation fails when using variable mapping in SAN field with a certificate template. |
|
1218573 |
Invalid config error occurs when running CLI script with metadata variables on Device Database in multi-vdom mode. |
FortiSwitch Manager
|
Bug ID |
Description |
|---|---|
|
1251586 |
VLAN interface allow-access settings may unset during upgrade from 7.2 to 7.6 FortiManager, refer to SN for more details. |
Others
|
Bug ID |
Description |
|---|---|
|
921784 |
Geography field is blank when creating firewall address type in FortiProxy ADOM Workaround: Create a CLI template with these addresses and add them to fw policy. |
|
1169450 |
When Backup ADOM is enabled and auto-sync is configured, FortiManager is not able to automatically retrieve the changes from FortiGate devices. Devices should remain in sync without the need for manual retrieval. |
|
1196043 |
Failed to create Alert Handlers or Reports on FortiManager when a Fortinet Fabric Connection is established on FortiAnalyzer to connect to the FortiManager device. Workaround: Go back to the specific ADOM on FortiAnalyzer and create the Alert Handlers or Reports there. After synchronization, the new entries should become available on FortiManager. |
| 1254367 |
FortiManager instances deployed on Azure may lose all dataincluding configuration, logs, and reportsif the VM is deallocated and subsequently reallocated. This may occur during Azure-level operations such as VM stop (deallocate) or SKU/size changes. Please refer to the Special Notices for more information. |
Policy and Objects
|
Bug ID |
Description |
|---|---|
|
1160047 |
Application control category "GenAI" is missing in FortiManager, but present in FortiGate. Workaround: Copy a FortiGate application list (Applist) from the CLI that includes Category 36, and insert it into a CLI template in FortiManager. Assign CLI template to FortiGate. |
|
1170814 |
The FortiManager Install Wizard displays a prominent Policy and Object Validation error for firewall addresses configured with IP 0.0.0.0. This should be presented as a warning rather than an error message. |