Details
-
Bug
-
Resolution: Done
-
Blocker
-
jboss-fuse-6.2.1
-
None
-
%
-
Description
New patching mechanism forgets installed feature and bundle that were installed before applying patch.
6.2 GA:
JBossFuse:karaf@root> features:install camel-jclouds JBossFuse:karaf@root> list | grep jclouds [ 271] [Active ] [ ] [ ] [ 80] jclouds Components Core (1.8.1) [ 272] [Active ] [ ] [ ] [ 80] jclouds blobstore core (1.8.1) [ 273] [Active ] [ ] [ ] [ 80] jclouds script builder (1.8.1) [ 274] [Active ] [ ] [ ] [ 80] jclouds compute core (1.8.1) [ 275] [Active ] [ ] [ ] [ 50] camel-jclouds (2.15.1.redhat-620133) JBossFuse:karaf@root> features:list | grep camel-jclouds [installed ] [2.15.1.redhat-620133 ] camel-jclouds camel-2.15.1.redhat-620133 JBossFuse:karaf@root> osgi:install -s mvn:org.apache.commons/commons-lang3/3.1 Bundle ID: 276 JBossFuse:karaf@root> list | grep Lang [ 276] [Active ] [ ] [ ] [ 80] Commons Lang (3.1.0)
After the patch is applied with all manual steps:
JBossFuse:karaf@root> list | grep Lang JBossFuse:karaf@root> JBossFuse:karaf@root> list | grep jclouds JBossFuse:karaf@root> JBossFuse:karaf@root> features:list | grep camel-jclouds [uninstalled] [2.15.1.redhat-621043 ] camel-jclouds camel-2.15.1.redhat-621043
This seems like a critical issue for the new patching mechanism
Attachments
Issue Links
- is incorporated by
-
ENTESB-4276 [Patch mechanism] Reported bugs [QA]
- Closed