Issue

SCR bundle with @Component(configurationPolicy = ConfigurationPolicy.REQUIRE) and configuration being <classname>-something.properties (org.jboss.fuse.integrations.Simple-context1.properties & org.jboss.fuse.integrations.Simple-context2.properties). Bundle and configuration running are in a child container in Fabric.

This setup should create two instances of "org.jbuss.fuse.integrations.Simple" using their respective configurations. If you deploy the bundle and then create the configurations this works perfectly, survives restarts and everything. But, if you change the Simple bundle version (1.0-SNAPSHOT -> 1.1-SNAPSHOT, for example) the bundle doesn't see the configurations anymore and stays UNSATISFIED. Restarting the bundle or the container won't help. If you edit and save a configuration the bundle will see it again.

If you edit the configuration while bundle 1.0-SNAPSHOT is deployed, bundle will see it fine. Then you change the bundle to 1.1-SNAPSHOT and the bundle won't see it. If you change the bundle back to 1.0-SNAPSHOT it will see it still. If you change the bundle to 1.1-SNAPSHOT and edit the configuration, bundle will see the configuration. Then you go back to 1.0-SNAPSHOT and bundle will see it still. So, editing the configuration seems to incorrectly associate with the version that is running at the time of the edit.

This has the consequence of having to manually edit every configuration (adding a dummy counter or something meaningless) after a bundle update, and having to manually check that all of intended configurations are running.