Skip to content

Known Issues

The following are the known issues as of 06/26:

Industrial Edge Management

Issue Troubleshooting Affected versions
Application status remains stuck in uploading after failed publish in IEM
  • IEM Pro V1: Delete the published application from the Admin Panel UI, then reupload the application again.
  • IEM Pro V2: Delete the application using the available API and then reupload and publish the application.
-
If a firmware update appears to be stuck in the "Updating" state under "Device Details" > "Firmware" but shows as "Canceled" on the "Job Status" page, it cannot be retriggered from the "New Experience" in Industrial Edge Management. The execution of the update can be initiated once more by employing either the standard UI of the Industrial Edge Management or the IECTL. -
Connecting an Edge Device to the IEM fails and the "Nginx configuration test failed" error message is displayed during activating the Edge Device phase. Check the DNS server configuration since the error message is DNS server related. The DNS server must be configured properly and reachable for the IEM. -
Field mac_address in apps docker compose is ignored. This is a bug of Docker Engine resolved with devices that use Docker Engine greater than 24.0. -
If the user does not have sufficient access rights to Identity & Access Management, the Identity & Access Management application will not load and the cursor will not stop. This error means that the user does not have permissions to work with Identity & Access Management. If you want to enable this for the user, you can follow the description in the "Assigning Roles" chapter and add the "realm-management - realm-admin" role to the user. -
If an Edge Device with a scheduled/active firmware update job is deleted from the IEM, the Edge Device itself may become unstable. Before deleting a Device from the IEM, make sure there is no scheduled/active firmware update job on the Device. -
Do not delete the user who has onboarded a Device. If the user is deleted, no applications can be downloaded to the Device because the Device cannot authenticate to the IEM's Docker Registry. - -
The email and username values are case-sensitive and will be automatically converted to lowercase in certain system components. To ensure proper functionality, always provide email and username values in lowercase letters. -
With IEM Pro v1.12.11 the USB-onboarding of an Industrial Edge Device fails. This issue is caused by the introduction of a new file name and a new value called expirationTime within the file.
There is a workaround in place you can use to overcome this situation:
  • Rename the onboarding file to device-<deviceId>, e.g. device-02ab9064847d4aba9106b7ac1064b8be. The deviceId is part of the onboarding file.
  • Remove the line "expirationTime":"1" from within the onboarding file.
Instead of the workaround you can also apply the hotfix IEM Pro v1.12.12. 		1.12.11
Job manager behaviour on application installation if application config detail is not updated to IEM According to the Job manager design
  • The job may fail if it cannot update the deployed configuration details on IEM. Nevertheless, the configuration is successfully downloaded, and the application starts working on IED.
  • The job will be marked as failed initially, with the option to retry. Upon retry, the job will be completed successfully.
-
Re-uploading device applications in IEM can lead to inconsistencies. When a device application is re-uploaded after deletion using a different upload method than the initial upload, metadata from the original upload can affect application handling in IEM (e.g. side-loaded applications may remain side-loaded, signature information may be lost, and the application version may not be publishable). -
Re-uploading device applications in IEM can lead to inconsistencies. When a device application is re-uploaded after deletion using a different upload method than the initial upload, metadata from the original upload can affect application handling in IEM (e.g. side-loaded applications may remain side-loaded, signature information may be lost, and the application version may not be publishable). -
The "Catalog" entry in the Device WebUI navigation bar is not currently intended to provide a device-level catalog landing screen in the IEM V2 setup. This is a known limitation of IEM V2 that does not affect device operation or application runtime. Selecting the catalog entry redirects users to the home screen. The catalog navigation will be reviewed and updated in a future release. IEM V2
With IEDK V1.28.0, static IP cannot be set if no valid Ethernet connection is detected.
  • No cable is connected to the device's Ethernet port.
  • The cable is connected to the device but not connected to any network equipment on the other end.
 Please connect the Ethernet cable to an active network device to proceed. IEDK v1.28.0

Industrial Edge Management Virtual

Issue Troubleshooting Affected versions
Software Update: When too many IEM Apps are installed, the update process might fail due to CPU resource restrictions without showing the reason. In particular, the update from version 2.4.x to 2.5.1 fails. Update all IEM Apps first, then apply the IEM Virtual update using the SWU file.
This sequence avoids resource conflicts caused by increased CPU requests.		 2.4.x β†’ 2.5.1
Software Update: For some IEM Virtual instances, the update stalls when bandwidth is limited. If an IEM Virtual update stalls due to limited network bandwidth, use the recovery key to access the Service and Maintenance applet through port 4443. You'll see the update in progress; cancel it to revert to the previous version for continued operation. Increase the bandwidth before attempting the update again. A solution to facilitate updates with limited bandwidth is under development. -
During an IEM Virtual update, "Unauthorized Access" and a Login button may appear, with the version still showing as the previous one. Refreshing the page may lead to errors like "The service is currently unavailable" and "The request was not carried out due to the client's lack of authorization."
  • Login using the Recovery key on port 4443
  • If errors persist, refresh the SaM UI page until the update progress reappears.
  • The Service and Maintenance UI will show the update process if it is still running.
  • After a few minutes, the update should complete, and all applications will become accessible.
 -
Software update logs are not appearing in the Logs console after an OS update.
  • Due to authentication timeouts during the update process, logs might not be visible during the whole process.
  • Start the update via port 4443, this will show the logs during the update process.
 -
Helmchart version in the OS Bar or IE Hub may not be displayed correctly after updating from 2.3.x A synchronisation problem introduced in 2.4.0 prevents the Helmchart version from being updated in the Hub or OS Bar. Reboot the virtual IEM to fix the problem. 2.3.x β†’ 2.4.0
DHCP: When using DHCP, make sure to always assign the same IP address to the IEM Virtual. Not doing so will result in an unreachable and unstable system. Assign a fixed IP address to the IEM Virtual instance. Ensure the DHCP does not dynamically change it. -
If an FQDN is provided, the IEM-APP cannot be reached via IP address anymore, only via the hostname. Ensure that the DNS server is available and working before providing an FQDN name. -
Network Limitations: For non FQDN setups, IP address, Netmask and Gateway cannot be changed after onboarding. Network Limitations: For non FQDN setups, IP address, Netmask and Gateway cannot be changed after onboarding. Keep the IEM Virtual instance up to date. This functionality will be available in upcoming versions. -
Newly configured IEM Virtual displays errors on first login or after reboot. This issue occurs because not all services are fully initialized. Wait a few moments for the services to start, and the errors will resolve themselves. -
Boot failure on IEM Virtual systems with ESXi v8 and SATA controllers: IEM Virtual systems may fail to boot after rebooting on ESXi version 8 if they are configured with a SATA hard disk controller. This issue occurs at the boot manager level, which prevents the VM from starting and redirects users to the Boot Manager screen. This issue is sporadic and primarily observed on fresh installations of IEM Virtual v2.6 or v2.7, as SATA is set as the default disk controller in these versions. This behaviour has not been observed on ESXi v7 or Hyper-V, nor does it affect systems using SCSI disk controllers. Workaround - Reconfigure the VM's disk controller from SATA to SCSI:
  • Power off the affected VM.
  • Edit the VM settings to remove the SATA adapter.
  • Add a SCSI controller (recommended type: VMware Paravirtual).
  • Reattach the disk(s) to the newly added SCSI controller.
  • Save the configuration and power on the VM.
Permanent Resolution: This issue will be resolved in IEM Virtual v2.8, which will ensure that new installations no longer face this issue. 		IEM Virtual on ESXi v8 with SATA controller.

Industrial Edge Device

Issue Troubleshooting Affected versions
Container-to-container communication may fail. This results in applications being unable to communicate with each other or with IE services, which may manifest as API errors or app UIs refusing to load. The issue is caused by Docker DNS resolution failures, due to incorrect domain name suffixes in the host's resolv.conf, which are inherited by containers. Force a DNS reconfiguration by updating the DNS configuration in any of the network interfaces from the UI (even if not needed). This forces the system to regenerate the resolv.conf file. The DNS configuration can be removed afterwards if it was not originally required. IEDOS 3.1.0