Resolved issues

The resolved issues listed below may not include every bug that has been corrected with this release. For inquiries about a particular bug, please contact Fortinet Customer Service & Support.

• For on-demand deployments on the AWS cloud with FortiRecorder VM, camerad crashed.

• A Duplicate IP camera status occurred after a discovered camera's IP address was changed, even if the camera did not currently have a duplicate IP address.

• Metadata stopped being recorded after some time if network connection errors were occurring repeatedly with the camera. This issue could be indicated by FortiCamera Cloud or FortiCentral charts with missing information, or by FortiRecorder log messages such as Failed to start 'metadata' recording for camera.

• While FortiRecorder had a tunnel with the camera, if the TCP network connection dropped, then camproxyd crashed.

• Messages about Dropped X segments occurred. These have been removed.

• When multiple people connected to view live video streams from an ONVIF (third-party) camera, the Error camera status occurred. The Viewing media profile setting was also empty. This issue only occurred if any previous software upgrades or downgrades included FortiRecorder 7.2.5.

• Incorrect permissions for the administrator profile named readonly_admin_prof allowed write access for execute commands in the CLI.

• Memory leak in the REST API

• On FortiRecorder400F with RAID where the hard disks are different sizes, if you upgraded from FortiRecorder 7.2.1 to 7.2.5, then FortiRecorder rebooted in emergency mode and the RAID stopped functioning. After running the CLI command exec raidlevel 0, the RAID was rebuilt and started to function again, but the RAID status was still Unknown.

• In the CLI, if you logged in as any administrator that was not admin but had SuperAdminProfile permissions, and then you created a new account and tried to set the password, it prompted you for the current password. However new accounts do not have an existing password yet.