Reported by Jason:

Scenario 1:

• Patch is applied to fabric via the FMC
• A new child container is created but it will not fully start and log shows the following error:

2013-06-07 09:41:56,209 | WARN | -71-047-thread-1 | FeaturesServiceImpl | res.internal.FeaturesServiceImpl 1044 | 19 - org.apache.karaf.features.core - 2.3.0.fuse-71-047 | Unable to add features repository mvn:org.fusesource.fabric/fuse-fabric/7.1.0.fuse-063/xml/features at startup
java.lang.RuntimeException: URL [mvn:org.fusesource.fabric/fuse-fabric/7.1.0.fuse-063/xml/features] could not be resolved.
at org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:195)
at org.apache.karaf.features.internal.FeatureValidationUtil.validate(FeatureValidationUtil.java:47)[19:org.apache.karaf.features.core:2.3.0.fuse-71-047]
at org.apache.karaf.features.internal.FeaturesServiceImpl.validateRepository(FeaturesServiceImpl.java:198)[19:org.apache.karaf.features.core:2.3.0.fuse-71-047]
....

Scenario 2:

• Patch is applied to standalone container
• Fabric is then attempted to be created:

FuseESB:karaf@root> fabric:create --clean --resolver localip --profile fmc
No user found in etc/users.properties or specified as an option. Please specify one ...
New user name: admin
Password for admin:
Verify password for admin:
Error executing command: Unable to create zookeeper quorum: Unable to create zookeeper server configuration

The culprit is the version.properties file in the fabric-core bundle: with a new build, that points to the new build number, but those artifacts don't necessarily exist in the patch. We should start with the base 047 build numbers to get the instances created so we can use the normal patching mechanism to update the other bundles.