Ability™ Developer Portal
Try Sandbox for free
Get a month of free access to ABB Ability™ Platform to learn and experiment!
API Playground
Play with ABB Ability™ Platform APIs (no time limits)

# Edge Installer Release Notes

# 2.4.0

# New Features

# [80305] - Replacement of Transparent Proxy

# New Functionality

Transparent proxy has been updated with new proxy technology based on V2Ray, this replaces existing proxy technology. The change is transparent to the applications.

Check out the updated Edge Software installation instructions to find out more.

# Resolved Issues

# [100568] - Edge nodes fail to be operational after rebooting

Upon reboot, Edge nodes failed to boot up successfully and was not operational. The abb-iot-edge-replay-netconf script needed to be executed manually in order to recreate the necessary Docker networks for the Edge to be in an operational state.

Executing the abb-iot-edge-replay-netconf script also used to cleanup Docker images, resulting in a need to re-download them.

We have now eliminated this manual step of running the script, and the abb-iot-edge-replay-netconf service will be triggered automatically when booting, and Docker image cleanup no longer occurs when running the script.

Note that by upgrading to the latest installer with this change, abb-iot-edge-replay-netconf will be executed automatically at the end of the upgrade, resulting in your Docker containers restarting.

# 2.3.2

# Resolved Issues

# [92144] - IP tables command fails when triggered from abb-edge-installer post installation script

IP tables command failed with latest docker (20.10.2). Post installation now handles upgrade scenarios properly.

# 2.3.1

# Resolved Issues

# [87514] - Docker network creation issue resolved

We are now checking for the successful creation of the docker network with proper CID, this will resolve this docker network being created with a different CID.

# [84929] - rsyslog service is disabled by default and is configurable via edge.env

Edge setup incorrectly enabled rsyslog when not configured in edge.env. To enable rsyslog, set the variable SYS_TRAIL_AGGREGATOR_HOST in edge.env configuration file to a valid syslog server address before running abb-iot-edge-setup.

# [86340] - Additional manual step in setting up edge in Ubuntu 20.04 is removed

Manual step required for creating mime.conf file in ubuntu 20.04 is now handled in abb-edge-iot-setup command.

# [90543] - IoT hub connection issue with latest docker (20.10.2) is now resolved

IP table issue with latest docker (20.10.2) is now handled in edge setup commands.

# [91129] - IP table issue with latest docker version (20.10.2) during upgrade procedure is resolved

IP table issue caused by latest docker version (20.10.2) during upgrade procedure is fixed.

# [86912] - Docker daemon debug logs is set to off by default

Docker daemon is now configured with debug as false, this is avoid docker demon logging more debug logs hence saves memory. It can be enable by setting "debug" to true in /etc/docker/daemon.json file in the edge.

# [90927] - New squid version upgraded and available for Ubuntu 18.04 and Ubuntu 20.04

Squid 3.5.27-1ubuntu1.10 is now available for Ubuntu 18.04 and Squid 4.10-1ubuntu1.3 is now available for 20.04.

# Known Issues

# [91127] - New version of docker has a warning that can be ignored until the next docker update

When executing an add-iot-edge-setup command with the latest docker version (20.10.2),
all docker commands display "WARNING: Error loading config file: .dockercfg: $HOME is not defined". This can be ignored. This is an issue with docker (docker bug https://github.com/moby/moby/issues/41890) and will be resolved in a future docker update.

# 2.3.0

# Improvements and enhancements

  • Swarm locking and unlocking was implemented

# Bug Fixes

  • [75125] Edge Docker swarm failure on ARM hardware because of executable format error in ARM
  • [75791] When netconf-replay is enabled, Network Bridge is not recreated after reboot
  • [75456] Edge proxy randomly fails to connect to TPM with an RPC failure when connecting to Secure Storage
  • [77410] Edge modules do not have full control over file storage due to permission problems

# Known Bugs

  • [73334] Edge Installer doesn't throw error even if DPCM fails at post operation

# 2.2.0

# Improvements and enhancements

  • Install a sub-directory called rpc underneath /var/ability, TPM software servers may use it to create domain sockets
  • Ensure that persistent data directories always remain read/writable to the system ability module group
  • A new environment variable EDGE_DEBUG=1, which enables shell debugging for Edge installation startup routines
  • If the Edge operator chooses to use DPCM to obtain a certificate offline, then the installer does not manipulate DPCM and TPM settings
  • Macvlan network is not created by default

# Bug Fixes

  • [66373] abb-iot-edge-setup ignoring all but 1st registry in IMAGEREGISTRIES variable
  • [62290] Factory reset doesn't work

# 2.1.2

# Improvements and enhancements

  • The installer enables MPKI to be used to provision Edge into 19.03 and 19.09 platform instances.
  • In the case of 19.03 make sure to use Edge Proxy with DPS support (abbability.azurecr.io/edge/proxy:2.2.12).

# 2.1.0

# Improvements and enhancements

  • A user can use the installer inside a Docker-in-Docker environment to provision Edge.
  • The installer can register the Edge in Principal Manager using an application token.
  • The installer allows reusing existing device certificate and module data so that Edge can be re-provisioned as an existing device.
  • The installer is capable of provisioning an instance of Edgenius.
  • Various other fixes and test automation enhancements.
  • Fixed an internal logical error that prevents firewall rules from being installed successfully
  • [51488] Daemons to configure the device hardware and relay communication between serial port devices and container services [WIP]

# Bug Fixes

  • [54254] BLOCK_INCOMING_CONTACT_ON_IFACE doesn't work for modules exposing ports

# 2.0.3

# Bug Fixes

  • [54253] BLOCK_INCOMING_CONTACT_ON_IFACE doesn't work for modules exposing ports

# 2.0.1

# Improvements and enhancements

  • [48253] Edge can be provisioned without TPM hardware as a fallback for testing purposes by setting SSL_ENGINE in edge.env to empty
  • Improved Docker startup sequence with fixes to the halted installation process
  • [45841] Improved configurator's package in order to further streamline continuous integration of the entire edge solution
  • [46556] Specified HTTPS port number for edge configurator in a stand-alone config file
  • [18864] Integrate DPS Client in Edge Proxy Container
  • [27778] Decouple Certificate enrollment and Provisioning
  • [20677] Improvement in Edge Security Inter Process communication
  • [32083] Access rules for TPM
  • [28655] Support for edge configurator

# Bug Fixes

  • [51010] Error messages when abb-iot-edge-setup is executed
  • [50451] abb-iot-edge-reset command does not remake firewall rules installed for BLOCK_INCOMING_CONTACT_ON_IFACE
  • [50740] The uninstaller did not disable abb-iot-edge service that was introduced with 19.09 release
  • [47443] Release candidate edge proxy shuts down after throwing error
  • [47439] Edge installer should trigger security services only upon successful TPM ownership
Last updated: 1/10/2022, 11:05:26 AM

← Edge Security →

Feedback