JBoss Fuse Full 6.1 EA 30 - No fabric commands after fabric creation!

[komododave]

We were using JBoss Fuse 6.1 EA 03 - Full successfully earlier this week.

After suffering a couple of bugs we've upgraded to the version 30 EA, made available on 1st August (yesterday).

We installed this version and ran our usual fabric:create command.

This terminated quickly and no errors/exceptions appeared in the logs.

But now there are no fabric commands available in the 'root' node karaf shell. So we can't container-list and so forth.

Any suggestions why...?

[komododave]

More details - we've narrowed down the cause..

Here's how we create a fabric:

JBossFuse:admin@root> fabric:create \

> --clean \

> --new-user admin \

> --new-user-role admin \

> --new-user-password admin \

> --zookeeper-password dayatthezoo \

> --resolver manualip \

> --manual-ip 10.97.6.186

Using specified zookeeper password:dayatthezoo

JBossFuse:admin@root> container-list

Command not found: container-list

As you can see, the fabric-commands feature's command set isn't available.

However, if we perform fabric creation without specifying --resolver.. --manual-ip... then everything works fine:

JBossFuse:admin@root> fabric:create \

> --clean \

> --new-user admin \

> --new-user-role admin \

> --new-user-password admin \

> --zookeeper-password dayatthezoo

Using specified zookeeper password:dayatthezoo

JBossFuse:admin@root> container-list

[id]                           [version] [alive] [profiles]                                         [provision status]

root*                          1.0       true    fabric, fabric-ensemble-0000-1                    

I should mention that the ip address we specify is a VIP address ("Virtual IP"). We have several VIPs on the host running fabric.

We've used this exact same setup previously, first with Fuse Fabric 7.1, then with JBoss Fuse 6.0 , and finally with JBoss Fuse 6.1 EA 03. All three of those earlier versions worked flawlessly with this exact fabric:create command using the exact same VIP.

Can you please confirm this is a bug and let us know of a workaround if you find one? Or else let us know when a new EA release with a fix is made?

[komododave]

No response on this - are we to simply ignore 6.1 for now then?

[stlewis]

The EA builds are pretty hit and miss, we're doing them regularly to keep an eye on the health of the build, but not all builds are going to work properly.  I think build 035 is in okay shape if you want to give that a try.