Release notes

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

Version 2.8.0

This version was released on March 27, 2024. Unless otherwise stated, all known issues and limitations of the previous version are still valid.

Features

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

Improvements

• Updated the device description file for use in CODESYS.
• Improved the usability of the remote connections icons in the workload list of the node details view. The icon was moved from the far right to the second spot on the left.
• Improved Management System navigation through implementation of selectable links in multiple areas. Refer to Improved navigation with selectable links in the Management System UI for a full list.
• Improved the system's caching and handling of state changes.
• Improved the system's handling and behavior when creating and editing user roles and permissions.
• Improved the system's communication through error messages in the UI.
• Improved behavior of checkbox elements in the node details view.
• Improved the search function for the deployment log. The log can be filtered by workload and workload version name.
• Improved the system's handling of ZIP files uploaded through Nerve DNA or CODESYS workload definition.
• Improved the system's speed of recognizing workload, deployment and node status changes.
• Minor UI improvements in Management System and Local UI.

Bug fixes

• Fixed a critical vulnerability caused by CODESYS v.3.5.17.20-7 that was used in the node image for Nerve 2.7.0. CODESYS components CmpApp and CmpAppBP were affected among others. Tags containing commands were not checked for size when sent to the PLC, meaning that attacks on storage were possible. This is now fixed with V3.5.19.40.
• Fixed an issue for Docker workloads where environment variables ending with = would not be handled properly.
• Fixed an issue where memory limit constraints would cause workloads carried over from previous versions to stop working properly.
• Fixed an issue where the login page would not adapt after turning LDAP authentication on or off and signing out.
• Fixed an issue where RAM usage would be displayed incorrectly for Docker Compose workloads.
• Fixed an issue where broken characters would appear in the product name during license activation when using Nerve as a VM.
• Fixed an issue where usage reports for the Management System could not be generated.
• Fixed an issue where re-applying a current target configuration through Nerve DNA would remove workloads that do not contain a hash in the configuration file.
• Fixed an issue where the Management System UI and Local UI would not load properly on Google Chrome incognito mode if the default language of the browser was not English.
• Fixed an issue where nodes with older versions would not have their node versions displayed in newer Management Systems.
• Fixed an issue where DNA reconfiguration would not continue after a restart, even though the flag had been set.

Known issues and limitations

• The AVX chipset feature is not available for Docker workloads running on node with the XEN hypervisor.
• Logs related to the Nerve Data Services Docker Compose workload are not shown in any OpenSearch dashboard.
• In some cases, undeploying Docker Compose and CODESYS workloads might fail, leaving the workload unremovable.
• In the host system, the genimg conf command does not set CPU pinning for the RTVM properly.
• It is possible to control workloads while the cancellation of a DNA configuration is in progress.
• The undeploying of workloads through Nerve DNA is not tracked in audit logs.
• When browsing a page containing a table, going back in the browser requires selecting the back button twice.
• When provisioning a new VM workload version via the API, it is possible to successfully provision a version with a malformed files array, rendering the workload unusable.
• Assigning a role to a user that only contains Nerve DNA permissions, causes the user to see the Logs tab in the node details view instead of the DNA tab.
• Deploying a workload through the Local UI that does not exist in the Management System, causes the workload to not be recognized in Nerve DNA operations.
• The deployment log detail view might show the wrong status for failed deployments that have been restarted.
• The Management System might give notifications of actions performed by other users, e.g. updating the resource reservation for running Virtual machine workloads.
• When two deployments are started shortly one after the other, the second deployment might have the status Done, even though the deployment has not started yet.
• The node details view does not scale properly if the window size is reduced to a very small size.
• User-defined notifications in the Management System will have a transparent background if no background image is defined.
• For workloads marked as released, remote connection settings can be defined and added, but not saved, causing an error.
• If two users happen to move a node from one element in the node tree to another at the same time, the node will show up twice in the node tree.
• Fixed an issue where Nerve internal networks would stop working. The installation process was adapted to prevent this.

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. Note that the new Nerve Connection Manager (v2.0.0) is only compatible with version 2.8.0 of the Management System.

Management System version	Node version	MS/node compatibility	Nerve Connection Manager (v1.0.13)	Nerve Connection Manager (v2.0.0)	Incremental node update	Full support
2.8.0	2.2.0
2.8.0	2.2.1
2.8.0	2.3.0
2.8.0	2.3.1
2.8.0	2.4.1
2.8.0	2.5.0
2.8.0	2.6.1
2.8.0	2.7.0
2.8.0	2.8.0

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: