Skip to content

Eclipse Kura 5.4.1
Compare
Choose a tag to compare
@MMaiero MMaiero released this 03 Dec 16:23
· 257 commits to develop since this release
KURA_5.4.1_RELEASE
d452c03
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Eclipse Kura - 5.4.1 - March 2024

Description:

This service release of Eclipse Kura includes the following changes:

  • Fixed NoSuchProviderException when creating new key pairs with keystores/v1 REST APIs
  • Fixed memory leak in org.eclipse.kura.linux.usb when unrecongnized udev events are received
  • Fixed data loss in Wire Record Store implementation for H2 when certain data types are stored

Target Environments:

Kura is released as pre-compiled binary installers for the following platforms:

  • Raspberry Pi 2/3/4 based on Raspberry Pi OS (32 bits) (Kura networking)
  • Raspberry Pi 3/4 based on 64 bits OS (Kura networking)
  • Intel Up Squared board running Ubuntu 20.04 (Kura networking)
  • Nvidia Jetson Nano board running Ubuntu 18 (Kura networking)
  • Generic Debian Package for x86_64 (NetworkManager)
  • Generic Debian Package for arm32 (NetworkManager)
  • Generic Debian Package for arm64 (NetworkManager)
    Kura is also available as a pre-built Docker container for Ubi 8 and Alpine

Bug Fixes:

  • 678d3dd - [distrib] added libudev.so.0 symlink [backport release-5.4.0] (#5167) (github-actions[bot])
  • 443f471 - Fixed unnecessary column type changes in H2DbWireRecordStoreImpl [backport release-5.4.0] (#5158) (github-actions[bot])
  • b0e4b54 - [linux.usb] memory leak on non-usb udev events [backport release-5.4.0] (#5138) (github-actions[bot])
  • e2123f3 - [BaseKeystoreService] Add missing key generator provider [backport release-5.4.0] (#5070) (github-actions[bot])

Target Platform Updates:

  • cca8257 - update org.eclipse.kura.linux.usb.version from 1.4.0 to 1.4.1-SNAPSHOT (#5145) (Marcello Rinaldo Martina)

Known Issues:

  • The firewall rule applied by the network threat manager that block uncommon TCP MSS values is not applied in the Nvidia Jetson Nano.
  • When the IPv6 network threat manager is disabled, the filtering on TCP fragments is disabled only after a reboot.
  • The republish.mqtt.birth.cert.on.modem.detect property in the CloudService configuration is not supported for devices that use NetworkManager. The property value is ignored.
  • When dnsmasq is used as DHCP server, only one file is used to store the leases.
  • When dnsmasq is used as DHCP server, the DHCP List field in the DHCP and NAT tab shows the leases for all the interfaces.
  • The system reboot command cannot be issued even with a privileged user in Debian Bookworm due to an OS issue related to the CAP_SYS_BOOT capability.
  • The Wi-Fi AP scanning may fail in Debian Bookworm on the first scanning attempt in the specific Raspberry PI profile. A forced rescan can succeed and properly display the available APs.
  • The nvidia-jetson-nano installer disables FAN protocol support due to compatibility issues (see #4593)
  • The nvidia-jetson-nano doesn't support the Unprivileged Command Service (see #3598)
  • isc-dhcp-server fails upon first Kura installation on Raspberry Pi Bullseye. This is due to how the isc-dhcp-server installer package is
    built and run immediately after installation.
  • An update to the sslmanagerservice where the pid of the keystoreservice is updated can lead to an error in the following reconnection.
    The issue impact is limited, if the dataservice reconnect option is enabled.
  • The implementation of the CryptoService performs encryption using a
    password that is hardcoded and published.
  • Modem: Ublox Lisa U201 may not be able to establish PPP connection when CHAP/PAP authentication is required.
  • WiFi on Raspberry Pi 2 has only been tested with WiPi WiFi Dongle (Realink RT5370 chipset) and official Pi USB WiFi Dongle (Broadcom BCM43143 chipset).
    AccessPoint WiFi mode not working for Broadcom chipset.
  • Hardware watchdog: not implemented on all platforms
  • Only one WAN interface is currently supported with old networking. A warning in displayed
    in the WEB UI if the user attempts to enable more than one WAN interface
  • #4212: Wrong order of BIRTH/APPLICATION certificates for custom APP IDs registration
  • #3972: Topic name validation: issue with names containing "//" (Cloud Subscriber)
  • #4141: Sometimes user is not logged in after changing password
  • #3796: Server manager does not close properly
  • #3211: Kura Docker | Bluetooth error in log during starting service
  • #3005: Kura Gets Stuck in Loading View if Services Clicked Too Fast
  • #2843: Access Banner Content All in One Line
  • #2747: No Spacing Between "Wire Components" and Error in Wire Graph
  • #2728: WireGraph Component Description Windows Too Wide
  • #2725: Different Pop-up Windows for Warnings
  • #2702: Error Message For Long Item Names Not Displayed Properly
  • #2696: Component Name Inteferes With Wire Graph Border
  • #2695: Component Names in Wires Not Limited
  • #2410: Deployment handler and URLs with many query parameters
  • #2038: [Kura 3.2.0 QA] Package uninstallation log
  • #1993: Search Domains Are Not Supported
  • #1663: Authentication Issue with Deploy V2
  • #1572: serial modbus has errors on some hardware
  • #1529: OSGI console is not redirected to Eclipse IDE with Kura 3.0
  • #1161: Incorrectly configuring a component can be irreversable.
  • #1128: [Kura 3.0.0 M1 QA] Unable to delete manually added CamelFactory services
  • #1016: ConfigurationServiceImpl creates duplicate instances
  • #797: Design of ServiceUtil is broken
  • #771: Web UI fails with INTERNAL_ERROR when WireHelperService is not registered
  • #654: Clean up static initialization around "modem" functionality
  • #645: Clean up internal dependencies in Kura
  • #522: [Net] Modem monitor should monitor interfaces, not modems
  • #486: Build environment broken on Windows
  • #406: Replace System.get* with calls to SystemService.getProperties
  • #329: [DEPLOY-V2] Review/refactoring needed
  • #297: [Status led] What connection instance controls the status led?
  • #253: Check if bundle contexes correctly unget services after invoking getService
  • #222: CloudConnectionStatusServiceImpl does not cancel workers on component deactivation

Changelog:

  • 678d3dd - fix(distrib): added libudev.so.0 symlink [backport release-5.4.0] (#5167) (github-actions[bot])
  • f26ed8b - chore: add Kura 5.4.1 release notes (#5161) (github-actions[bot])
  • 9b07371 - chore: automated uptick to 5.4.1 (#5160) (github-actions[bot])
  • 443f471 - fix: Fixed unnecessary column type changes in H2DbWireRecordStoreImpl [backport release-5.4.0] (#5158) (github-actions[bot])
  • cca8257 - build(distrib): update org.eclipse.kura.linux.usb.version from 1.4.0 to 1.4.1-SNAPSHOT (#5145) (Marcello Rinaldo Martina)
  • b0e4b54 - fix(linux.usb): memory leak on non-usb udev events [backport release-5.4.0] (#5138) (github-actions[bot])
  • a8d3a33 - chore: Added known issue for birth publish on modem detect (#5134) (Pierantonio Merlino)
  • e2123f3 - fix(BaseKeystoreService): Add missing key generator provider [backport release-5.4.0] (#5070) (github-actions[bot])
  • 9348921 - chore: automated uptick to 5.4.1-SNAPSHOT (#5038) (github-actions[bot])
Assets 14
Loading