Predix Edge Release Notes 2.5.0 | Edge 2.9 Documentation

Upgrade Path

Predix Edge OS must be installed incrementally; you cannot skip a minor release (i.e., if you are running version 2.3.3, you must first install 2.4.0 and then 2.5.0). You do not have to install every patch release (indicated by a change to the third digit in the release number).

General

Consolidated Release Notes: Release notes for all Predix Edge components (i.e., OS, Agent, PETC, etc.) will now be published as one, rather than being separated by component.

Predix Edge Tested Components

This release was tested using the following Predix Edge components:

Edge OS 2.5.0
Cloud gateway 20.3.0
OPC-UA Adapter 20.2.0
OSI-Pi Adapter 20.2.0
EGD Adapter 1.3.0
MQTT Adapter 1.3.0
Modbus Adapter 1.3.0
Predix Historian MQTT Collector 2.2.0
IGS Adapter 1.1.0

New Features and Enhancements

This release contains the following new features and enhancements:

Syslog Forwarding: A new feature now available in Predix Edge Manager allows you to forward syslog events from an Edge device to a remote syslog server with a severity-based filter.

Configure Maximum Transmission Unit (MTU): The ability to set a value for MTU has been added to the setup of Network Adapters within the Predix Edge Technician Console (PETC). MTU configuration is available in both DHCP and Static modes; the default value is 1500 bytes.

OS Upgrade to Yocto Warrior: Predix Edge OS has been upgraded to Yocto Warrior to deliver bug fixes, security fixes, and new functionality.

Bug Fixes

The following bug fixes are implemented in this release:

Disrupted File Transfers: If a file transfer from Edge Manager to a device is disrupted due to a network outage for example, the transfer will resume automatically once connectivity is restored.

System Proxy Changes: The system restart after a proxy change will automatically stop and restart the applications on next reboot, resolving the issue of system proxy changes not being propagated into deployed applications.

Secure Command Channel: Previously an abrupt loss of power while deploying a secure command channel-enabled application may result in an inability to manage applications that leverage the secure command channel. Now, when this condition is encountered, the previously existing applications will continue to work but the interrupted application will need to be re-deployed.

Timestamp Not Updated after OS Upgrade: The Last Updated timestamp in PETC has been removed from the user interface.

Known Issues

This release has the following known issues:

Successful Factory Reset Returns Failure Message: After performing a factory reset via PETC, an error message may pop up indicating the operation Failed to reset device; however, the factory reset will have been successful.

Docker Apps Flooding Logs: A Docker application that floods the logs can cause system performance to degrade, resulting in the Docker applications restarting.

Serial Port Bootlog: A qemu- or vmware-based OS will output the bootlog out of the serial ports. This can cause problems if they are connected to physical hardware.

Device Clock Modifications: If a device’s clock is modified to a time prior to when it was first initialized, all deployed applications will be stopped and all system applications will run after the device reboots.

Application Configurations: Applications will not be able to read application configuration files created without read permissions. Ensure that configuration files have read permissions prior to zipping them in preparation for uploading them to Edge Manager or PETC.

Invalid Log Level: A cloud gateway with an invalid log level will not forward data to the cloud and will not generate any log messages.

Data Not Forwarding When OPC-UA Adapter Fails to Connect to Broker: In some instances, when the client id is not specified in the application configurations, two separate applications may have identical mqtt client IDs, resulting in the applications failing to connect to the broker and data not being forwarded.