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 7.6.7.
Existing known issues
The following issues have been identified in a previous version of FortiManager and remain in FortiManager 7.6.7.
AP Manager
|
Bug ID |
Description |
|---|---|
|
1086946 |
The FortiAP upgrade via FortiManager may fail (on FortiGate 7.6.1). The process could stop at the controller_download_image step or experience a prolonged stall, eventually resulting in a timeout. |
Device Manager
|
Bug ID |
Description |
|---|---|
|
1264581 |
Interfaces from other VDOMs appear when creating zones in Device Manager > Network > Create Zone, FortiManager is working in ADOM Mode Advanced. |
Others
|
Bug ID |
Description |
|---|---|
|
1143100 |
Unable to add physical FortiProxy to FortiManager. |
|
1196043 |
Failed to create Event 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 Event Handlers or Reports there. After synchronization, the new entries should become available on FortiManager. |
|
1217534 |
During an upgrade of an FortiGate-HA cluster via FortiManager, if the disk-check feature is enabled, it may cause all cluster members to reboot simultaneously. This can result in an unexpected traffic interruption. Workaround: To prevent this issue, disable the disk check before performing the upgrade: config fmupdate fwm-setting set check-fgt-disk disable end |
|
1277049 |
Installation may fail because FortiManager repeatedly pushes the default "set annex a" configuration to FortiGate DSL devices. |
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. |
|
1200063 |
Failed to update EMS tags from EMS cloud server on FortiManager v7.6.x. |
| 1285742 | FortiManager fails to update when ZTNA server configuration changes are made during Service/Server Mapping modifications. |
| 1297846 | Application match field becomes empty when FortiManager installs policies after application signature deletion. |