Details
-
Bug
-
Resolution: Done
-
Blocker
-
jboss-fuse-6.2.1
-
None
-
%
-
Description
It is not really a blocker but more like enhancement to the patch mechanism. When adding patch to the fabric environment using the patch:add command that was used previously in standalone mode, you get this output.
JBossFuse:karaf@root> patch:add file:/home/fuse/jboss-fuse-full-6.2.1.redhat-070.zip
[name] [installed] [description]
jboss-fuse-full-6.2.1.redhat-070 false jboss-fuse-full-6.2.1.redhat-070
Then if you continue with patching process the installed tag is always set to false. The command patch:fabric-install doesn't change this tag nor upgrading some container to a version with applied patch.
In my opinion it would be better to track name of the version with applied patch or discard this output and patch:list command when fabric is created if it is possible. At the moment this information is misleading.
Attachments
Issue Links
- is incorporated by
-
ENTESB-4276 [Patch mechanism] Reported bugs [QA]
- Closed
- relates to
-
ENTESB-5682 Status of installed 6.2.1 R2 and R3 patch on standalone container is false
- Closed