-
Bug
-
Resolution: Done
-
Major
-
jboss-fuse-6.2
-
None
-
%
-
fabric:join ignores --non-managed option when joining standalone container into existing fabric.
JBossFuse:karaf@root> fabric:create -r localip --global-resolver localip --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
Using fabric:join command from standalone container with manually changed karaf.name property:
JBossFuse:karaf@node> fabric:join -r localip --non-managed 172.16.116.7:2181 Ensemble password: JBossFuse:karaf@node>
Check connected standalone container in fabric and we get that the Managed is still set to true:
JBossFuse:karaf@root> container-list
[id] [version] [type] [connected] [profiles] [provision status]
node 1.0 karaf yes fabric success
root* 1.0 karaf yes fabric success
fabric-ensemble-0000-1
jboss-fuse-full
JBossFuse:karaf@root> container-info node
Name: node
Version: 1.0
Connected: true
Type: karaf
Root: true
Ensemble Server: false
Managed: true
Process ID: 3444
Resolver: localip
Network Address: 172.16.116.34
Local Network Address: 172.16.116.34
Public Network Address:
Local Hostname: rjakubco-fuseqe8
Public Hostname:
SSH Url: 172.16.116.34:8101
JMX Url: service:jmx:rmi://172.16.116.34:44444/jndi/rmi://172.16.116.34:1099/karaf-node
Http Url: http://172.16.116.34:8181
Jolokia Url: http://172.16.116.34:8181/jolokia
Blueprint Status: started
Provision Status: success
JBossFuse:karaf@root>
