-
Notifications
You must be signed in to change notification settings - Fork 26
Known Issues
This page is intended to describe any known bugs or issues in current and recent OpenLI releases, and provide some advice on how to avoid or mitigate them.
I'll try to keep this up to date, but feel free to get in touch with me (@salcock) directly if you spot anything that needs updating.
This problem can occur if you had installed an older version of OpenLI (pre-1.1.0) and are attempting to upgrade it (or any other packagges on your Debian/Ubuntu machine). You may see an error message much like this:
W: Failed to fetch https://dl.cloudsmith.io/public/wand/libwandio/deb/ubuntu/dists/jammy/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C84FDFFA361F3D61
To fix this, run the following commands:
curl -1sLf 'https://dl.cloudsmith.io/public/wand/libwandio/gpg.C84FDFFA361F3D61.key' | gpg --dearmor > /tmp/foo
sudo mv /tmp/foo /usr/share/keyrings/wand-libwandio-archive-keyring.gpg
sudo apt update
You should now be able to run apt commands again without seeing errors for the libwandio repository.
You may run into this issue after you upgrade to libtrace 4.0.16.
Affected Versions: 1.0.9-1 and earlier
Bug Status: Resolved once you upgrade your OpenLI packages to 1.0.9-2 or later.
Mitigation: If upgrading OpenLI is not an option, downgrading libtrace to 4.0.15 should also work.
Note that if your OpenLI packages have been coming from our bintray repository, you will need to change over to our cloudsmith repository instead. The bintray service is closing down, so we no longer upload new packages there -- see the "Installing" pages on this wiki for instructions.
Affected Versions: 1.0.9
Bug Status: Fix will be included in the 1.0.10 release.
Mitigation: Restart the collector after changing configuration rather than using the reload mechanism -- just avoid doing this while you have an active intercept running.
Affected Versions: 1.0.4 - 1.0.9
Bug Status: Fix will be included in the 1.0.10 release.
Mitigation: Delete and then re-add the intercept with the new agencyID instead.