Details
-
Bug
-
Resolution: Done
-
Major
-
jboss-fuse-6.3
-
None
-
%
-
6.3 Sprint 4 (Mar 28 - Apr 29)
Description
1. create "custom" 6.2 - with new patch mechanism wget jboss-fuse-full-6.2.0.redhat-133.zip unzip -o jboss-fuse-full-6.2.0.redhat-133.zip zip -r jboss-fuse-full-6.2.0.redhat-133-custom.zip jboss-fuse-6.2.0.redhat-133/ 2. use this custom zip to create a new root with fabric 3. add the new patching mechanism to root: fabric:version-create 1.0.1 fabric:profile-edit --repository mvn:io.fabric8.patch/patch-features/1.2.0.redhat-630015/xml/features default 1.0.1 fabric:profile-edit --feature patch --feature patch-core default 1.0.1 fabric:container-upgrade 1.0.1 root 4. create a SSH container container-create-ssh --user fuse --password fuse --host jawa50.tpb.lab.eng.brq.redhat.com first-ssh-container 5. create a child of root (not necessary for the issue) container-create-child root first-child-container 6. copy the fabric8-karaf zip from ssh to root (with suffix -custom) - the folder /home/fuse/patch-mechanism-test is shared between the two ssh: cp -f /home/fuse/containers/first-ssh-container/fabric8-karaf-1.2.0.redhat-133.zip /home/fuse/patch-mechanism-test root: mv /home/fuse/patch-mechanism-test/fabric8-karaf-1.2.0.redhat-133.zip /home/fuse/fafram/jboss-fuse-6.2.0.redhat-133/system/io/fabric8/fabric8-karaf/1.2.0.redhat-133/fabric8-karaf-1.2.0.redhat-133-custom.zip 7. add patch patch:add http://fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/ea/org/jboss/fuse/jboss-fuse-full/6.3.0.redhat-015/jboss-fuse-full-6.3.0.redhat-015.zip 8. create a new patched version and upgrade root version-create 1.1 patch:fabric-install --upload --username fafram --password fafram --version 1.1 jboss-fuse-full-6.3.0.redhat-015 container-upgrade 1.1 root 9. root requires restart, so it is restarted 10. patch:fabric-synchronize 11. upgrade ssh container-upgrade 1.1 first-ssh-container 12. ssh requires restart, so it is restarted, but it does not come online again
Grzegorz's comments:
<ggrzybek> the problem is that I added "service.geoip.enabled = false" option at the bottom of etc/system.properties
<ggrzybek> and when SSH container is created, the creation scripts adds there some properties, like (the most important) zookeeper.url = jawa49.tpb.lab.eng.brq.redhat.com:2181
<ggrzybek> so we have merge conflict
Attachments
Issue Links
- is related to
-
ENTESB-4408 [Patch mechanism] Change hawtio patching to new patch mechanism
- Closed