You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Serge Starovoitenkov (Jira)" <ji...@apache.org> on 2021/09/26 22:23:00 UTC
[jira] [Created] (KARAF-7258) Cellar bundle-update with new
location value not working when bundle-version differs
Serge Starovoitenkov created KARAF-7258:
-------------------------------------------
Summary: Cellar bundle-update with new location value not working when bundle-version differs
Key: KARAF-7258
URL: https://issues.apache.org/jira/browse/KARAF-7258
Project: Karaf
Issue Type: Bug
Components: cellar
Affects Versions: cellar-4.2.1
Environment: Karaf 4.2.9
Cellar 4.2.1
Reporter: Serge Starovoitenkov
When using cellar:bundle-update command or CellarBundleMBean.update(String group, String id, String location)
and
the bundle on the new location has version different from installed one
we get correct local state (bundle updated and the version changed) and wrong cluster state (old version and new location) because we don't read bundle manifest when updating from new location. but only change the location (seeĀ [https://github.com/apache/karaf-cellar/blob/2a44d1a53b15c23781bcb4a49a27ddfeda3d401e/bundle/src/main/java/org/apache/karaf/cellar/bundle/management/internal/CellarBundleMBeanImpl.java#L384] andĀ [https://github.com/apache/karaf-cellar/blob/2a44d1a53b15c23781bcb4a49a27ddfeda3d401e/bundle/src/main/java/org/apache/karaf/cellar/bundle/shell/UpdateBundleCommand.java#L94] )
Considering the OSGi specification allows bundle version changing while updating from new location and Karaf itself works it out as expected, the mentioned behavior of Cellar seems to be a bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)