Background:

1. We use Nexus repos for maven and don*t have direct internet access on the fabric host.

2. On an existing RC 047 fabric we created a new profile my-fmc which had lone parent fmc. Within my-fmc profile we added the config file org.ops4j.pax.web.properties. Within this we specify org.ops4j.pax.web.listening.addresses=vip-ip. This IP address is one for the VIP the fabric has been created on. We then exported this profile through FMC, generating my-fmc.zip .

Procedure:

We untar the RC 047 fabric tarball on the VIP whose IP was configured above.

Then launch bin/karaf from the extracted installation root.

Then run the following command. Note that an import directory is specified which contains only my-fmc.zip.

fabric:create --clean --new-user admin --new-user-role admin --new-user-password ourPass --zookeeper-password ourZkPass --import-dir /dir/containing/my-fmc"

Following this, running:

fabric:container-list

produces the following output:

id version alive profiles provision status

root 1.0 true fabric, fabric-ensemble-0000-1, fmc error - java.lang.IllegalArgumentException: Unable to find feature fabric-commands

However this feature is clearly present. We know this because:

i. Profile fmc can be installed offline, and my-fmc merely extends it and adds no feature dependencies.

ii. Running find -regex '.fabric-commands.' in the fabric installation directory locates the relevant JAR:

./fuse-fabric-7.1.0.fuse-047/system/org/fusesource/fabric/fabric-commands

./fuse-fabric-7.1.0.fuse-047/system/org/fusesource/fabric/fabric-commands/7.1.0.fuse-047

./fuse-fabric-7.1.0.fuse-047/system/org/fusesource/fabric/fabric-commands/7.1.0.fuse-047/fabric-commands-7.1.0.fuse-047.jar

Is this is a bug?