Kevan Jahanshahi created UNOMI-767: -------------------------------------- Summary: Custom bundle is uninstall when restarting Key: UNOMI-767 URL: https://issues.apache.org/jira/browse/UNOMI-767 Project: Apache Unomi Issue Type: Bug Affects Versions: unomi-1.7.1 Reporter: Kevan Jahanshahi
Using a Unomi cluster (1.7.1) (3 nodes) When we develop and deploy a custom bundle in */etc/deploy* on all the nodes. Restarting a node make the bundle uninstall, here is the only log we have when the node is restarting: {code:java} 2023-04-18T10:48:01,282 | INFO | activator-1-thread-4 | BlueprintExtender | 20 - org.apache.aries.blueprint.core - 1.10.3 | Destroying container for blueprint bundle org.XXX.unomi.custom-bundle-unomi/1.0.3 {code} And attempt to *touch* the jar file from */etc/deploy* to make it reinstall: {code:java} 2023-04-18T10:49:11,478 | WARN | fileinstall-/opt/unomi/deploy | fileinstall | 12 - org.apache.felix.fileinstall - 3.7.4 | Failed to update bundle: /opt/unomi/deploy/muna-unomi-1.0.3.jar with ID 268. The bundle has been uninstalled {code} Then last option was to remove the jar from {*}/etc/deploy{*}: {code:java} 2023-04-18T10:51:26,591 | WARN | fileinstall-/opt/unomi/deploy | fileinstall | 12 - org.apache.felix.fileinstall - 3.7.4 | Failed to uninstall bundle: /opt/unomi/deploy/muna-unomi-1.0.3.jar with id: 268. The bundle has already been uninstalled {code} So something is wrong with custom bundles in cluster and I don't know if we have the same behavior in standalone. -- This message was sent by Atlassian Jira (v8.20.10#820010)