Release 29.0.5 contains a number of bug and security fixes, as well as a few enhancements.
It include an update to the latest Log4j2 release. It is not believed that we are vulnerable to the Log4j issues fixed in these newer releases, but are updating anyway just to be sure.
For a high-level overview of what has changed in Horizon 29, see What’s New in OpenNMS Horizon 29.
The codename for Horizon 29.0.5 is Kingfisher.
- TimescaleDB extension can’t added to existing opennms DB. (Issue NMS-13441)
- Enlinkd API response extremely slow for some nodes (Issue NMS-13507)
- Customer is not able to view Topology (Issue NMS-13851)
- Very large node caches can cause telemetry adapters to fail on Sentinel (Issue NMS-13859)
- Permission check in ./install -dis flags unwriteable files in the .git directory - redux (Issue NMS-13860)
- CVE-2021-45105: Update to Log4j 2.17.0 (Issue NMS-13868)
- upgrade to log4j2 2.17.1 and pax-logging 1.11.13/2.0.14 (Issue NMS-13878)
- Consolidate all IPC features into one / need conf.d changes (Issue NMS-13610)
- Add metrics about twin communication (Issue NMS-13649)
- Extend SnmpMetadataProvisioningAdapter configuration to support exact OID matches (Issue NMS-13842)
- Support an endpoint that allows to access parts of resources (Issue NMS-13863)
- Minion Kafka docs missing reference to custom.system.properties (Issue NMS-13885)