Setting whitelist.bypass=true exhibits the same failures (bundle NOT whitelisted)[0]. So issues with the regexp can be ruled out as the main cause.
I wonder if we should install the startupfilter(disabler) bundles? That might delay the TestClient to wait until the system is (more) ready. Ultimately I agree with Bertrand though. We need to understand the root cause. Regards Julian [0] https://builds.apache.org/job/sling-contrib-extensions-contextaware-config-integration-tests-1.8/214 On Tue, Nov 29, 2016 at 10:25 AM, Julian Sedding <[email protected]> wrote: > I mostly agree with Bertrand's interpretation. > > However, I a config can be applied early (i.e. registered with config > admin), but components are still lazily instantiated. Does anyone know > if there is a guarantee that components are configured (activated) > before they become visible? > > If there is no such guarantee, there may be a time-window when they > are visible with default config before they are properly configured. > > Regards > Julian > > PS: I just committed an experimental change to set > whitelist.bypaass=true in order to rule out any regexp issues. > > On Tue, Nov 29, 2016 at 9:36 AM, Bertrand Delacretaz > <[email protected]> wrote: >> On Mon, Nov 28, 2016 at 10:47 PM, Robert Munteanu <[email protected]> wrote: >>> ...That would be SLING-6305 [1] I guess. ... >> >> I haven't debugged deep down yet but intuitively it should be possible >> to apply very early in the startup phase all the configs that are >> supplied by the provisioning model. >> >> If someone has time to look at why this is not the case that might >> help solve a number of similar issues + avoid multiple component >> restarts when configs appear late. >> >> -Bertrand
