After Migration from 4.0.0 to 4.1.1 openhab totaly down is in Nirvana / working with openhabian

[splatch (Łukasz Dywicki)]

@Duke_Jones

Unfortunately, I also have no idea what the cause could be.

Cause is shown in logs which are attached:

FrameworkEvent ERROR org.osgi.framework.BundleException: Could not resolve module: org.connectorio.addons.ui.iconify
2024-01-15 17:02:54.290 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed to refresh bundles after processing config update
java.lang.IllegalStateException: Resource has no uri

The iconify addon (which I made and published over marketplace) is bound to OH3 while OP activated OH4. I believe he just need to remove this addon for update time and bring back another version when he is done with update.

Issue has nothing to do with SD or SSD, its hardly to call it update issue since it happens in polluted conditions.

@jimtng

An interesting point. Perhaps we need to make some sort of formal versioning system for add-ons to avoid this very case. i.e. Addons need to have some sort of manifest to mark maximum version and OSGi (or openhab) wouldn’t proceed to load it if this is violated.

The addons/ folder is a special case as it is pulled by Apache Karaf/Felix Fileinstall itself. It functions as hot deployment directory, beyond direct control of openHAB. However all fileinstall does for us (in case of OH) is getting JARs/KARs and calling bundle.install(uri_of_the_file) or karService.install(..).

There are decade old utilities which could permit static validation of manifest entries. However for a start I’d simply advice to just move installation of third party addons to a separate thread which does not interfere with boot/framework thread.