Predix Edge Agent Release Notes 2.2.0

These are the new features and known and resolved issues for Predix Edge Agent, version 2.2.0.

New Features

This release contains the following new features:
General
  • Ability to execute commands from Edge Manager into an application.
  • Ability for an application to expose capabilities and related status to Edge Manager.
  • Ability to implement an application that supports the Predix.Edge.AnalyticEngine capability.
  • Ability to execute the following commands from Edge Manager:
    • Run Top
    • Run ifconfig
    • Set Polling Interval

Known Issues

This release has the following known issues:
Docker Apps Flooding Logs
A Docker application that floods the logs can cause system performance to degrade, resulting in the Docker applications restarting.
Application Data Directory Ownership
If ownership of the application/data directory is modified by the application, subsequent updates or redeployments of the application will fail.
  • Workaround: If you must change the owner of a directory, leverage a sub-directory under the /data directory, rather than the root directory.
  • If the workaround was not implemented and attempts to update or redeploy the application fail, you must delete and re-add the application to update it. This will result in a loss of the content in the /data and /config directories.
Application Upgrade Failure
An application that creates a volume mount at /data in the Docker build file can also cause an upgrade of the application to fail.
  • Workaround: Remove the /data or /config volume mounts from the Docker build file. These mounts will automatically be created at deployment..
  • If the workaround was not implemented and attempts to update or redeploy the application fail, you must delete and re-add the application to update it. This will result in a loss of the content in the /data and /config directories.
Extended Power Off Period
Docker will not properly start if a system with a working clock has been powered off for more than three months. Existing applications will be stopped and will not be able to be re-started. A log entry will indicate that "swarm component could not be started" with a x509 certificate expired error if the device is in this state.
To avoid this issue, do not power off a device for more than three months. If you encounter this issue, contact technical support.

Upgrade Notes

  • edge-agent-runner is now a reserved image name; any application that utilizes an image named ‘edge-agent-runner’ will be rejected during deployment.
  • edgeAgent/ is now a reserved topic in the MQTT broker; applications utilizing topics under this hierarchy may no longer work.
  • edgeApp/ is now a reserved topic in the MQTT broker; applications utilizing topics under this hierarchy may no longer work.