Loading...
Loading...
Users may observe that the firmware version displayed in the UI still shows as 2.2.0.0 after upgrading NativeEdge endpoints firmware from version 2.2.0.0 to 3.0.0.0. Despite a successful upgrade, the system continues to report the older version due to the absence of a stamping catalog for version 3.0.0.0. This mismatch can cause confusion during validation or audits, as it may appear that the upgrade did not complete. However, there is no impact on functionality because the firmware components in versions 2.2 and 3.0.0.0 are identical. The behavior is consistent across endpoints using 3.0.0.0.
The firmware version mismatch occurs because 3.0.0.0 uses the same firmware components as 2.2.0.0 but does not have its own stamping catalog. During a reboot of NativeEdge Orchestrator or hzp-firmware-update-svc restart, the system uses the available 2.2.0.0 catalog for stamping. This results in the firmware version being displayed as 2.2.0.0 in the UI, even though the NativeEdge Orchestrator is on 3.0.0.0. The behavior is expected and does not affect functionality, as the components are identical. This is a known limitation of the 3.0.0.0 release. Also, when a device is upgraded using the 3.0.0.0 firmware bundle, the version reflects as 3.0.0.0. However, if a new device is onboarded with the same firmware components, it may still show version 2.2.0.0. This is because the firmware version stamping relies on the XML definitions located under config/firmware/ inside the hzp-ece-firmwareupdate-svc pods of the Edge-Orchestrator. Moreover, if the 3.0.0.0 firmware bundle is applied without rebooting the NativeEdge Orchestrator, the displayed version continues to show as 3.0.0.0.
There is no functionality impact because the firmware payload is identical in v2.2.0.0 and 3.0.0.0. No resolution is needed. If customer plan to upgrade to later NativeEdge releases, see "additional info" section below.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.