Predix Edge Release Notes 2.7.0

These are the new features, enhancements, and known and resolved issues for the 2.7.0 release of Predix Edge.

Upgrade Path

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

New Features and Enhancements

This release contains the following enhancements:
Yocto
The system has been upgraded to Yocto Dunfell 3.1.
Static IP Address for VM First Interface
The Predix Edge OS VMs now have a default static IP address for the Predix Edge Technician Console. See Installing Predix Edge OS Virtual Machine
IGS Protocol Adapter Support Discontinued
Predix Edge no longer supports the IGS protocol adapter.

Known Issues

This release has the following known issues:
RFC 1918 Private Address Space
If you upgrade from Predix Edge 2.4.0 or earlier to Predix Edge 2.7.0, private addresses will not be resolved. Use the following steps as a workaround for this issue.
  • SSH access is required
  • edit /etc/dnsmasq.conf to comment out (put "#" in front of):
    • bogus-priv
    • stop-dns-rebind
  • restart the dnsmasq.service
    • systemctl stop dnsmasq.service
    • systemctl start dnsmasq.service
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.
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.
MAC Address Displays as 'unknown'
There is a bug in Predix Edge OS that causes PETC to display MAC addresses as "unknown" for all ethernet interfaces. To obtain the actual MAC address for an ethernet interface, execute the "Run ifconfig" command from Predix Edge Manager. The MAC address will be in the resulting text file output that can be downloaded from the Predix Edge Manager Device Commands tab.
File Permissions on the config-xxxx.json File
Mac/Linux users should ensure that the file permissions on the config-xxxx.json file are 644 prior to adding to the zipfile for deployment to your Predix Edge Device. Other file permissions may result in the Edge Application being unable to start up and the journalctl log file will show error messages containing stream error and Unable to parse JSON file.

Resolved Issues

The following issues were resolved in this release:
Fixed Vulnerabilities
This release contains fixes for the following security vulnerabilities:
  • CVE-2021-3156
  • CVE-2021-3449
  • CVE-2021-3450