Occasionally not all blueprints installed from profile

Issue

We use blueprint files to provide datasources and connection factories.

We've noticed that sometimes not all blueprints associated with a profile are installed to a container. There are no exceptions observed in the logs, and using "container-stop/start" can result in a different number of bundles being installed, although this typically fixes the problem.