Resolved issues
The following issues have been fixed in 7.6.5. To inquire about a particular bug, please contact Customer Service & Support.
AP Manager
|
Bug ID |
Description |
|---|---|
|
1173274 |
FortiManager is trying to enable ddscan when it is not enabled on ADOM db, device db, and AP Manager profile. |
|
1174004 |
After FortiManager Cloud's upgrade, FortiManager may suggest to " |
|
1178251 |
FortiManager is attempting to unset the auth-cert on the wireless-controller VAP during every installation. |
| 1198357 | AP Manager encounters issues with central AP management because some channels may not be supported. |
| 1204035 | FAP-231K is not supported by FortiManager. |
Device Manager
|
Bug ID |
Description |
|---|---|
|
970157 |
FortiManager Cloud is attempting to install SNMP configurations that are not supported by the FortiGate VM, such as power-supply-failure, temperature-high, and voltage-alert. |
|
1102790 |
FortiManager pushes the |
|
1152287 |
HA group-id not inherited from CSV file or from pre-run script. |
| 1155534 | An error occurs when disabling the IP Range Managed by IPAM option on the VLAN interface. |
|
1173182 |
CLI Template Installation Fails with error message "SSID rename not allowed". |
|
1176785 |
Getting error while importing certificate 'no write permission to do this operation'. |
| 1188313 | The Device Asset Identity Center displays an incorrect last-seen time, and the hardware information should remain consistent with the FortiGate. |
|
1198163 |
When installing an SD-WAN static route via a template, the push fails with a duplicated route error. |
| 1201252 | The static route template triggers duplicate-route errors during installation because duplicate routes, including those using blackhole interfaces, are not allowed. |
| 1202695 | FGT90G/91G Gen2 are not supported in Device Model. |
| 1208974 | Device count is not correct. |
| 1215090 | Unable to retrieve correct setting of device-identification in system interface. |
| 1219062 | "sla-compare-method" still available on SDWAN rules when load balance is enabled. |
FortiSwitch Manager
|
Bug ID |
Description |
|---|---|
|
1193285 |
When changing the name of a FortiSwitch from FortiSwitch Manager, the next Installation will reset the ports configuration of the switch to default configuration. |
Global ADOM
|
Bug ID |
Description |
|---|---|
|
1182076 |
Renamed global objects are not reflected with their new names in associated policies. |
|
1183101 |
Not able to delete firewall objects from the global database after upgrading FortiManager from 7.2 (7.2.10) to 7.4 (7.4.7). |
Others
|
Bug ID |
Description |
|---|---|
| 1077126 | The FortiExtender API connection status is returning incorrect value for the FortiExtender device when in an "unknown" state. |
| 1099773 | FortiExtender Page 'Data Usage' value does not display the updated values. |
| 1146320 | After creating the SSID and assigning it to the FortiExtender profile, the configuration is not pushing to the FortiGate, resulting in an installation failure. |
| 1158842 | The FortiManager Cloud dashboard FortiGuard license status does not display the same data as shown on the FortiGuard page. |
| 1177268 | FortiFirewall License Validation fails on FortiManager configured as Local FDS. |
|
1199504 |
When Workspace is in Workflow mode, the fmg-admin may observe "You have no write permission to do this operation" error message when attempting to modify an interface. |
| 1201751 | Unable to add managed FortiAnalyzer to FortiManager Cloud. |
| 1211261 | Users might experience "Attempting to reconnect" messages every few minutes while logged in to the GUI. |
|
1217951 |
FortiManager Cloud may not recognize the 1000F serial number as valid for applying the corresponding Device Blueprint, preventing the CSV file from being loaded. |
| 1224258 |
The new EMS version (7.4.5) has upgraded its communication protocol from HTTP/1.0 to HTTP/2. Unlike HTTP/1.x, HTTP/2 does not return a traditional 200 OK text response, so older FortiManager Cloud versions that expect this format cannot interpret the new HTTP/2 replies. Because of this, older FortiManager Cloud builds will not be compatible with the latest EMS version. |
Policy and Objects
|
Bug ID |
Description |
|---|---|
| 1083504 | FortiManager Cloud attempts to configure the service in the ISDB6 policy (IPv6), but FortiOS rejects it, causing the installation to fail. |
| 1139663 | When using the Install Object(s) function after renaming an object, FortiManager pushes the old object name to the firewall policy. |
| 1156437 | No interface mapping listed when importing config for a device (device mapping undefined). |
| 1169058 | Installation might fail to these devices "FGT/FWF-30G/31G" due to some unsupported syntax. |
| 1170381 | Unable to create new section "Add
Section" in policy after upgrading FortiManager Cloud while using interface pair
view mode. Operation "Add Section" triggers nothing. Field
"label" or "global-label" are empty. |
| 1174618 | After importing the policies and objects from the FortiGate, even though the FortiManager Cloud settings were selected, the configuration status for all FortiGates changed to Modified. |
| 1181585 | "Where Used" feature does not function. |
| 1185738 | During the auto-linking process, FortiManager Cloud attempts to push a policy package containing Internet-Service based rules, but the FortiGates outdated ISDB causes the installation to fail. |
| 1196308 | EMS server security posture tags are not fully synchronized with FortiManager Cloud; ZTNA tags comment are missing. |
|
1198075 |
Upon any modification, policy installation will result in attempt to purge dns-database even though no changes are made to dns database. |
| 1211860 | Existing Objects shown as "Not found" in "Where Used". |
| 1212118 |
Reinstalling policy packages for more than three devices may cause the Application Security Console to crash. |
| 1215309 | Installation hang when pushing configurations to firewall groups. |
| 1215349 |
FortiManager may delete policies or settings during device installation due to concurrent database interactions from tasks like auto-updates, policy installs, or HA-related updates running simultaneously. |
| 1218648 | The Alternative Resources setting under AWS connector is not pushed to FortiGate. |
System Settings
|
Bug ID |
Description |
|---|---|
| 1086386 |
Unable to save changes for SNMP users in FortiManager Cloud if more than one notification host is configured. |