-
Bug
-
Resolution: Done
-
Major
-
jboss-fuse-6.2
-
None
-
jboss-fuse-full-6.2.0.redhat-118, openjdk-7
I am unable to join standalone container to running fabric using the fabric:join command with manualip resolver. It seem that the command will change IP address of the root container. Openstack machines are used for this scenario.
Root container:
JBossFuse:karaf@root> fabric:create -r manualip --manual-ip 172.16.116.18 --wait-for-provisioning Waiting for container: root Waiting for container root to provision. JBossFuse:karaf@root> container-list [id] [version] [type] [connected] [profiles] [provision status] root* 1.0 karaf yes fabric success fabric-ensemble-0000-1 jboss-fuse-full JBossFuse:karaf@root> container-info Name: root Version: 1.0 Connected: true Type: karaf Root: true Ensemble Server: true Managed: true Process ID: 11410 Resolver: manualip Network Address: 172.16.116.18 Local Network Address: 172.16.116.18 Public Network Address: Local Hostname: rjakubco-fuseqe5 Public Hostname: SSH Url: 172.16.116.18:8101 JMX Url: service:jmx:rmi://172.16.116.18:44444/jndi/rmi://172.16.116.18:1099/karaf-root Http Url: http://172.16.116.18:8181 Jolokia Url: http://172.16.116.18:8181/jolokia Blueprint Status: started Provision Status: success JBossFuse:karaf@root> fabric:info Fabric Release: 1.2.0.redhat-118 Web Console: http://172.16.116.18:8181/hawtio Rest API: http://172.16.116.18:8181/cxf/fabric8 Git URL: http://172.16.116.18:8181/git/fabric/ Jolokia URL: http://172.16.116.18:8181/jolokia ZooKeeper URI: 172.16.116.18:2181 Maven Download URI: http://172.16.116.18:8181/maven/download/ Maven Upload URI: http://172.16.116.18:8181/maven/upload/
Standalone container on different machine with IP address 172.16.116.17:
JBossFuse:karaf@root> fabric:join --resolver manualip --manual-ip 172.16.116.17 -f 172.16.116.18:2181 node2 Ensemble password: JBossFuse:karaf@root> Please wait while JBoss Fuse is loading... _ ____ ______ | | _ \ | ____| | | |_) | ___ ___ ___ | |__ _ _ ___ ___ _ | | _ < / _ \/ __/ __| | __| | | / __|/ _ \ | |__| | |_) | (_) \__ \__ \ | | | |_| \__ \ __/ \____/|____/ \___/|___/___/ |_| \__,_|___/\___| JBoss Fuse (6.2.0.redhat-118) 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. JBossFuse:karaf@root>
This is how the root container looks after the fabric:join command:
JBossFuse:karaf@root> container-list
[id] [version] [type] [connected] [profiles] [provision status]
node2 1.0 karaf no fabric
root* 1.0 karaf yes fabric success
fabric-ensemble-0000-1
jboss-fuse-full
JBossFuse:karaf@root> container-info root
Name: root
Version: 1.0
Connected: true
Type: karaf
Root: true
Ensemble Server: true
Managed: true
Process ID: 8953
Resolver: manualip
Network Address: 172.16.116.18
Local Network Address: 172.16.116.17
Public Network Address:
Local Hostname: rjakubco-fuseqe4
Public Hostname:
SSH Url: 172.16.116.18:8101
JMX Url: service:jmx:rmi://172.16.116.18:44444/jndi/rmi://172.16.116.18:1099/karaf-root
Http Url: http://172.16.116.18:8181
Jolokia Url: http://172.16.116.18:8181/jolokia
Blueprint Status: started
Provision Status: success
JBossFuse:karaf@root> container-info node2
Name: node2
Version: 1.0
Connected: false
Type: karaf
Root: true
Ensemble Server: false
Managed: true
Process ID:
Resolver:
Network Address:
Local Network Address:
Public Network Address:
Local Hostname:
Public Hostname:
SSH Url:
JMX Url:
Http Url:
Jolokia Url:
Provision Status:
Both logs seems to be fine and don't show any errors or problems. Creating fabric with localip resolver seems to be even worse when joining the standalone container using the manualip.
I am also unable to join standalone container to fabric using other resolvers, but manualip changing the IP address of root container is really strange. It will be probably better to check the whole fabric:join command.
- is duplicated by
-
ENTESB-3897 Unable to join a container to fabric when the container name is changed in fabric:join command
-
- Closed
-
- relates to
-
ENTESB-4880 fabric:join command doesn't work with specified name in fabric environment
-
- Closed
-