fabric:container-create-child command throws java.rmi.NoSuchObjectException: no such object in table

Issue

• Below are the steps we used:

1. Unzip jboss-fuse-full-6.1.0.redhat-379.zip
2. Modify karaf.name in system.properties
3. Add admin user to users.properties
4. Start fuse

$ cd /opt/fuse/jboss-fuse-6.1.0.redhat-379/bin/
$ ./fuse

5. Wait to make sure it started
6. From the karaf console execute

>patch:add file:///opt/fuse-installer/jboss-fuse-6.1.0.redhat-379-r2-611423.zip

7. Wait for few minutes until cpu load drops to almost 0%
8. From the karaf console execute

>patch:install jboss-fuse-6.1.0.redhat-379-r2

9. Received the error "Command not found: shell:if", ignored it
10. Shut down Fuse

>shutdown -f

11. Start Fuse

$ ./fuse

12. Created fabric

> fabric:create --clean --wait-for-provisioning
Waiting for container: rt-root-esb10
Waiting for container rt-root-esb10 to provision.
Error executing command: Unable to create zookeeper server configuration

13. Ignored this error (as recommended in the link you posted)
14. Shut down Fuse

shutdown -f

15. Start Fuse

$ ./fuse

16. Everything looks ok, all fabric commands work

However, it looks like, after creating the fabric, the root container is no longer using patched version, and we need to apply the same patch again to root container and all others as described here

Patching a Container in a Fabric

Question 1. Is root container really no longer using patched version after fabric creation?
Question 2. If answer is yes, can we then skip all the steps 6-11 above and just use the instructions from the
Patching a Container in a Fabric

ISSUE
Then we repeated steps 1-11 on another two servers, and joined the fabric created on the first server:

fabric:join --zookeeper-password admin2 MELEXHESB10:2181

Then we created an ensemble:

fabric:ensemble-add -f rt-root-esb11 rt-root-esb12

As a result, we had these containers in fabric:

JBossFuse:admin@rt-root-esb10> fabric:container-list 
[id]                           [version] [connected] [profiles]                                         [provision status]
rt-root-esb10*                 1.0       true        fabric, jboss-fuse-full, fabric-ensemble-0001-1, forloop-common success
rt-root-esb11                  1.0       true        fabric, fabric-ensemble-0001-2, forloop-common     success
rt-root-esb12                  1.0       true        fabric, fabric-ensemble-0001-3, forloop-common     success

Then we installed all 3 containers as linux service using the

wrapper:install

Everything looks fine so far, but then we tried to create child containers. First was created successfully, second failed

JBossFuse:admin@rt-root-esb10> fabric:container-create-child rt-root-esb11 esb-app-node01
The following containers have been created successfully:
Container: esb-app-node01.
JBossFuse:admin@rt-root-esb10> fabric:container-list | grep esb-app-node01
   esb-app-node01               1.0       true        default                                            success
JBossFuse:admin@rt-root-esb10> fabric:container-create-child rt-root-esb12 esb-app-node02
The following containers have failed:
      <not available>: java.rmi.NoSuchObjectException: no such object in table

I attached all the log files (ensemble.zip)