Resolved issues
The following issues have been resolved in FortiADC 7.2.0 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 0879270 | Httproxy crashes when deleting a hidden field name using the wrong object. |
| 0878635 | GCP spinlock issue. |
| 0874221 | NFR request to change the position of GUI drop-down menu items for "log out" and "reset configuration" to align with the GUI of other Fortinet products. |
| 0874118 | After upgrading to FortiADC 7.0.4, Automation alert email subjects default to "FADC_Alert". |
| 0873838 | In the GUI, HA remote IP monitor allowed to create children table before the parent table is saved. |
| 0873773 | Memory leak issue caused by configuration synchronization after upgrading to FortiADC 6.2.5. |
| 0871641 | Loss of connectivity between FortiADC and FortiAnalyzer due to hardware platforms attempting to use a certificate that is not available to them. |
| 0868982 | WCCP did not work with VDOM. |
| 0867226 | The Cookie Security policy Max Age unit is based in minutes in the GUI, but the value that is inserted to the cookie is based on seconds, which means the given range would be incorrect. |
| 0865060 | SNMP does not respond for power supply trap. |
| 0862865 | Layer 7 virtual server frontend SNI incorrectly contains real server local certificate. |
| 0862575 | File upload fails with Antivirus engine error when scanning JSON attachments due to access violation in the last byte of the body. |
| 0858336 | CORS Protection deny access even for legitimate traffic specified in Allowed Origin. |
| 0857019 | FortiADC console displays kernel related messages when execute
reload command is executed. |
| 0855871 | Upgrade failed due to unsupported "firewall nat-snat" IPv6 configuration. |
| 0852948 | Unable to switch between polling/epoll mode in FortiADC 7.x.x due to shell user restrictions. |
| 0850561 | SLB stops responding to SSL requests due to WAF function handling special filename in multi-part, which contains invisible characters and longer than 255. |
| 0848745 | Health check does not fail even when the real server is not configured with the services due to some daemon being unable to register the cmdb event. |
| 0847611 | High spike in CPU usage and random reboots. |
| 0845338 | FortiADC reporting wrong interface speed with SNMP. |
| 0826635 | FortiADC crashed after changing the virtual server type from Layer 4 to Layer 2. |
| 0826540 |
In the GUI, failed to append child list when configuring Automation. This results when an alert type has reached the maximum entry capacity. The current maximum is 256 entries for each alert type, as categorized in the backend CLI:
|
| 0823165 |
HA synchronization issues caused by comments. In an HA environment, if you are using a predefined automation configuration, resetting the configuration through the GUI (using the reset button) or unsetting comments through CLI will cause the HA synchronization to fail whenever a device reboots and rejoins the cluster. Using the GUI reset button resets the predefined configuration values to the predefined default values, all except the comments value which is set to the default value on the backend. For example, if using the HA predefined configuration, the reset will result in In the CLI, if |
| 0805652 | Cannot revert predefined automation configurations to default values without affecting HA environment. |