Release notes

This page contains a list of features, changes, known issues and known limitations of the Nerve releases.

Version 2.10.0

This version was released on June 18, 2025. Unless otherwise stated, all known issues and limitations of the previous version are still valid.

Features

Refer to What's new in 2.10.0? for more information on new features.

Improvements

• Added the ability to share direct URLs to specific nodes or deployed workloads.
• Secure IDs of a nodes are now obfuscated in the Management System interface to enhance data protection and prevent unintended exposure of sensitive information according to IEC 62443-4-2.
• Added option to restart workloads during DNA reconfiguration from the MS UI.
• Replaced Filebeat and Metricbeat with Fluent Bit for log and metric collection on both the Management System and nodes, with data visualized through OpenSearch (see here).
• Removed restrictions on memory allocation and CPU core usage for workloads.

Bug fixes

• Fixed a high severity vulnerability where certain attacks on endpoints were not being recorded in the audit logs.
• Fixed an issue where LDAP functionality was not working on the Management System.
• Fixed an issue where a workload release warning was incorrectly displayed when adding a remote connection or label to a released version.
• Fixed an issue where deployed workloads were not correctly sorted by timestamp on the node detail page.
• Fixed an issue where the Management System did not respond to a missing MQTT heartbeat.
• Fixed an issue where the Nerve Connection Manager was using an incorrect connection link.
• Fixed an issue where the DNA status was not updating on a selected node in the Management System.
• Fixed an issue where VM backup restoration did not fail when the hash was incorrect.
• Fixed an issue where workload files were not properly removed when deleting a workload in the Management System.
• Fixed an issue that was preventing remote connections due to a corrupt configuration in the settings file.
• Fixed an issue where inconsistent timezones were displayed on the update log page in the Management System.
• Fixed an issue where Docker networks failed to start correctly after a node update or a node reboot.
• Fixed an issue where scrollbars overlapped in the remote connection listing of a Node.
• Resolved a high-severity vulnerability in the Management System where the Reset Credentials API exposed detailed information about user existence, potentially enabling user enumeration attacks.

Known issues and limitations

• On rare occasions, a node's file system can become corrupted due to a hard power cycle.
• Failure of the Docker daemon is not currently reported or indicated in the Management System or on the LocalUI on the node.
• The creation process for VHDX-based VM workloads fails when version conversion is attempted.
• In some cases, the CODESYS workload may remain stuck in the 'Idle' state after deployment.
• In rare scenarios, CODESYS workload deployment may be unsuccessful due to underlying system conditions.
• Preseed configuration does not support full CODESYS setup on unknown hardware.
• Log rotation is currently not supported for CodeMeter logs.
• Disabling LDAP on the Management System does not automatically disable corresponding LDAP users on the node.
• When a user logs out of the Management System, the audit log records an incorrect message and result.
• When a Docker Compose workload is stopped as part of a DNA reconfiguration process, the stop action is not recorded in the audit logs.
• When the Local Repository configuration is saved via the Local UI, the password is returned in plaintext in the response to a GET API request.
• Workload Audit Logs are currently not stored on dedicated storage, which does not comply with the requirements outlined in IEC 62443-4-2.
• The Local UI does not display progress information during volume export operations.
• When a VM snapshot creation fails, the audit log records an incorrect message that does not accurately reflect the failure.
• The audit log displays an incorrect timezone after changing the serial number of a node.
• Deleting an docker image tag during deployment may lead to a non-functional workload due to inconsistencies in image availability.
• The garbage-collect command fails to remove image manifests that do not have any associated tags in the registry.

Compatibility matrix

Refer to the table below for information on the compatibility between different components of the Nerve system with the current version of the Management System.

For more information on technical limitations (), and requesting assistance with setting up older versions in the current version (), contact a sales representative or write an issue through the TTTech Industrial support portal.

Scaling and performance limitations

This release has been tested to perform within the following scaling boundaries: