[Patch mechanism] Upgrading child container reverts user.properties to karaf default version

Starting Fuse GA with modified user.properties and creating fabric with child container, you are able to connect to child container using admin/admin.

admin=admin,admin,manager,viewer,Monitor, Operator, Maintainer, Deployer, Auditor, Administrator, SuperUser

After installing patch with new patch mechanism, upgrading root container and then child containers, you are still able to connect to child container using admin/admin.

But if you call patch:fabric-synchronize before the upgrade root and child then after upgrade the child container has user.properties like this:

karaf = karaf,_g_:admingroup
_g_\:admingroup = group,admin,manager,viewer,webconsole

So it is logical that connecting to this child container doesn't work anymore with admin/admin but only with karaf/karaf.

I am not sure if this really blocker because the fabric environment is working without problem and both containers have new versions of bundles. It is just strange behavior that can cause problems to customer so for now I created it as blocker. Your opinions?