Details
-
Bug
-
Resolution: Done
-
Blocker
-
jboss-fuse-6.2
-
None
-
%
-
Description
In ER6 patch:apply finally works as it should but when upgrading container to created version with applied patches, container is unable to upgrade to specified version in some degree.
First of all upgrading is trying to upgrade the container for almost 6-7 minutes ( both jdk7 and jdk8, with internet or without) then it just resets itself.
JBossFuse:karaf@root> version-create 1.1
Created version: 1.1 as copy of: 1.0
JBossFuse:karaf@root> patch-apply --version 1.1 file:/home/rjakubco/Programing/jbossqe-fuse/fuse-tests/karaf-related-tests/patch-tests/karaf-124.zip
7 minutes of downloading of container
[id] [version] [type] [connected] [profiles] [provision status]
root* 1.1 karaf yes fabric downloading (1 pending)
fabric-ensemble-0000-1
jboss-fuse-full
[id] [version] [type] [connected] [profiles] [provision status]
root* 1.1 karaf yes fabric updating (stopping bundles)
fabric-ensemble-0000-1
jboss-fuse-full
_ ____ ______
| | _ \ | ____|
| | |_) | ___ ___ ___ | |__ _ _ ___ ___
_ | | _ < / _ \/ __/ __| | __| | | / __|/ _ \
| |__| | |_) | (_) \__ \__ \ | | | |_| \__ \ __/
\____/|____/ \___/|___/___/ |_| \__,_|___/\___|
JBoss Fuse (6.2.0.redhat-123)
http://www.redhat.com/products/jbossenterprisemiddleware/fuse/
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Open a browser to http://localhost:8181 to access the management console
Create a new Fabric via 'fabric:create'
or join an existing Fabric via 'fabric:join [someUrls]'
Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown JBoss Fuse.
Error in initialization script: Command not found: if
JBossFuse:karaf@root>
JBossFuse:karaf@root> container-list
[id] [version] [type] [connected] [profiles] [provision status]
root* 1.1 karaf yes fabric downloading (1 pending)
fabric-ensemble-0000-1
jboss-fuse-full
JBossFuse:karaf@root> list | grep Karaf
[ 11] [Active ] [ ] [ ] [ 80] Apache Karaf :: OSGi Services :: EventAdmin (2.4.0.redhat-620124)
[ 14] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Admin :: Management (2.4.0.redhat-620124)
[ 34] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Shell :: Console (2.4.0.redhat-620124)
[ 35] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Shell :: Various Commands (2.4.0.redhat-620124)
[ 36] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Shell :: OSGi Commands (2.4.0.redhat-620124)
[ 37] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Shell :: Log Commands (2.4.0.redhat-620124)
[ 38] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Shell :: PackageAdmin Commands (2.4.0.redhat-620124)
[ 39] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Shell :: Development Commands (2.4.0.redhat-620124)
[ 40] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Shell :: ConfigAdmin Commands (2.4.0.redhat-620124)
[ 42] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Management :: Server (2.4.0.redhat-620124)
[ 56] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Shell :: SSH (2.4.0.redhat-620124)
[ 60] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Admin :: Core (2.4.0.redhat-620124)
[ 62] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Deployer :: Blueprint (2.4.0.redhat-620124)
[ 63] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Deployer :: Spring (2.4.0.redhat-620124)
[ 64] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Deployer :: Wrap Non OSGi Jar (2.4.0.redhat-620124)
[ 85] [Active ] [ ] [ ] [ 80] Fabric8 :: Karaf Features Service (1.2.0.redhat-123)
[ 87] [Active ] [ ] [ ] [ 80] Fabric8 :: Runtime :: Container :: Karaf :: Registration (1.2.0.redhat-123)
[ 152] [Active ] [Created ] [ ] [ 80] Apache Karaf :: Features :: Command (2.4.0.redhat-620124)
[ 153] [Active ] [ ] [ ] [ 80] Fabric8 :: Karaf Commands (1.2.0.redhat-123)
[ 255] [Active ] [Created ] [ ] [ 80] hawtio :: Karaf terminal plugin (1.4.0.redhat-123)
As you can see container is not successful provisioned even after long 7 minutes but karaf bundles were updated to version 124 as they should. Log is clear without any exception or problem. Applying two similar patches almost doubles the 7 minutes timeout to 13 minutes with the same result.
It has probably something to do with fixing the patch:apply command in https://issues.jboss.org/browse/ENTESB-3189 and fixing the search in repos. I think this long waiting time without successful provision is really problematic.
