Dwarfguard version 2.0.1 "Keeper patch 1"
- status: Actual
- released at: 2026-05-03
- supported modes of operation:
- production: Yes
- free usage: Yes
- 2.0.1 build 0:
- SHA-256 sum: 6e517d467d82e476ec565bec076182cf8220cc15b4f03844d99e63fe70bbd953
- supported deployment modes:
- DT SAAS / DT Cloud / DT Server Managed: Yes / Yes / Yes
- Partner SAAS / Partner Cloud / Partner Server Managed: Yes / Yes / Yes
- Customer self-managed: Yes
- Private network: Yes
- support planned: major release, support via patch releases 2026+
- upgrade supported from:
- target audience: All
- showcase video: Dwarfguard 2.0 showcase video
- paper: Dwarfguard 2.0.0 paper
Release notes - known issues, changes since last release
- Version 2.0.1 is a first patch on the stable 2.0 branch.
- This patchlevel fixes all issues except not removing a defunct link button to download customized agent as that functionality is obsolete and will be removed in 2.1.0 release.
- Both Debian GNU/Linux 12 and Debian GNU/Linux 13 are supported as underlaying OS
Featured changes
- Incorporated fixes for issues (see issue details in Release 2.0.0 page - Known issues):
- DCL DB export can be broken under some condition
- Alert on missed contact metric using "greater than" operator is created as invalid
- Tunnel connect button for Webtunnel is not shown if Python extended libraries are not installed
- When updating license to another one with worse parameters (e.g. less devices, expires sooner etc.), GUI cannot be used for that.
- Log entries timestamps on device do not contain timezone
- Additional changes
- Implemented emergency service shutdown (and restart) when a very rare corner case error occurs in MariaDB/DB connector library (MariaDB internal error not propagated to Dwarfguard which invalidates some prepared queries but leaving DB connection itself working).
Known issues (updates with bugs being reported)
- "Download preset agent" button in Device details leads to error 500 for OpenWRT devices
- Reported: 2026-04-11 for version 2.0.0
- Impact: None (obsolete functionality handled otherwise in 2.0.0)
- Severity: None
- Status: Unfixed. The button will be removed in 2.1.0
- Details: In historic Dwarfguard versions (0.7.x and 0.8.x), a specific device-preset agent was needed to properly reinstall the agent on a device so that this would not loose its Device ID. Nowadays, this is handled by Machine ID, which is generated automatically and stays the same for the same device even on agent reinstall. This functionality is obsolete and should have been removed even in version 1.0.0 however it stayed there as an left over. There is no point in using this functionality.
- Workaround: Do not click on the button as it does not provide anything of value.
- When deleting a device, GUI shows "Device was not deleted" (while it was)
- Reported: 2026-05-27
- Impact: Cosmetic/confusion
- Severity: None
- Status: To be investigated and fixed
- Details: When a user deletes a device, the device is deleted but the GUI shows error message stating "Device was not deleted". NOTE that device being deleted actually means device is marked for deletion and no longer visible for user in GUI. The final device deletion (from the Database) happens on next Dwarfguard service restart however that is only a technicality and the device slot is freed immediately after the device deletion by the user (does not require service restart). The GUI error being shown has no impact on the device deletion process, it is simply a confusing (and wrong) message being shown.
- Workaround: None / Ignore this message
- Changes Tracker is too slow responding when there are many data entries
- Reported: 2026-06-05
- Impact: Using changes tracker is complicated because of this
- Workaround: Use limited date window when working with the Changes Tracker
- Workaround2: use Grafana/FluxDB for tracking device metrics history
- Workaround3: (for admin): check indexes on data_change_log table, add indexes as needed (recommendation to be specified)
- Severity: Low (only Changes Tracker is affected)
- Status: To be investigated and improved.
- Details: This is caused by combination of behavior change for DCL in Dwarfguard 2.0 and low I/O performance on VM. The history metrics are now saved to the SQL DB as well in contrast to Dwarfguard 1.0 where only the changes were saved. This change was due to the fact that when using a limited date window, the device metrics that has not changed during the window are not present there, therefore potentially limiting the usage of looking for extremes in the date window (if the device with the extreme value in the metric had no change in the value, it was not visible in that date window). This causes more data in the DCL table in SQL DB and combined with low I/O performance on some VMs, it causes delays in the UI when waiting for data processing.
- Fix: The logging behavior to be updated so that all changes in the metrics are logged into the SQL DB and also there is at least one value per day stored as well so that there are some data even if the value does not change but the amount of data (especially for not changing metrics) is significantly lowered.
- Alert that is both raised and past is shown only as raised on the dashboard
- Reported: 2026-06-09
- Impact: If an alert is active for some devices, the devices that no longer has this alert triggered but had this alert triggered in past (past alert) are not shown on the Dashboard as an alert is shown as Raised only.
- Severity: Low (once the higher priority stuff (raised alert) is handled, the past alert shows up, correctly listing all affected devices)
- Status: To be investigated