I tried building the app from source code but did not reproduce the problem. I guess this matches your experience - this happens only during an 'upgrade'.
Can you please give me a set of steps to reproduce? Ideally without MongoDB, but if that's required leave it in :-) Thanks, Robert On Wed, 2020-01-22 at 22:08 -0500, Carlos Munoz wrote: > I double checked and we do have the mapping. We copied all the > provisioning > files from the commit you recommended earlier [1] and deployed like > that. > > In fact, you can see our provisioning files here: [2] We are only > adding a > single file with our own bundle and configurations. > > [1] > https://github.com/apache/sling-org-apache-sling-starter/commit/c4f6e3b > [2] > https://github.com/redhataccess/pantheon/tree/upgrade-sling-bundles/pantheon-slingstart/src/main/provisioning > > On Wed, Jan 22, 2020 at 4:54 PM Robert Munteanu <romb...@apache.org> > wrote: > > > On Wed, 2020-01-22 at 16:16 -0500, Carlos Munoz wrote: > > > Thanks for the tip Daniel! > > > > > > Robert - we were able to successfully package the sling starter > > > with > > > the > > > latest definitions as you pointed, but when deploying on top of > > > an > > > existing > > > database we started getting a JCR error: > > > > > > javax.jcr.LoginException: Can neither derive user name nor > > > principal > > > names > > > for bundle org.apache.sling.jcr.resource [152] and sub service > > > observation > > > > > > We don't get the same error when deploying on a fresh database. > > > > It seems that you have some missing service user mappings. Those > > might > > be required by newer versions of the bundles that you just > > consumed. In > > the Sling Starter the current mapping is defined at [1]. > > > > Does adding that as a configuration to your application help? > > > > Thanks, > > Robert > > > > > > [1]: > > https://github.com/apache/sling-org-apache-sling-starter/blob/7eac121fc3f00c95ef5b8ac38133f6796a4a6c08/src/main/provisioning/sling.txt#L199-L202 > > > >
