Konrad, I just anonymized one of the sequences (of dozens): *WARN* [OsgiInstallerImpl] org.apache.sling.installer.core.impl.PersistentResourceList Removing stale resource TaskResource(url=launchpad:resources/install/0/content-package-a-1.1.0.zip, entity=content-package:groupx:packagenamex, state=UNINSTALL, attributes=[org.apache.sling.installer.api.tasks.ResourceTransformer=:25:22:1170:, package-id=groupx:packagenamex:1.1.2, sph-option=INSTALL, Bundle-Version=1.1.2], digest=1111111111), overwritten by TaskResource(url=launchpad:resources/install/0/content-package-a-1.1.0.zip, entity=content-package:groupn:content-package-a, state=INSTALL, attributes=[org.apache.sling.installer.api.tasks.ResourceTransformer=:25:22:1170:, package-id=groupn:content-package-a:1.1.0, Bundle-Version=1.1.0], digest=1111111111) *INFO* [OsgiInstallerImpl] org.apache.sling.audit.osgi.installer Uninstalled content package TaskResource(url=launchpad:resources/install/0/content-package-a-1.1.0.zip, entity=content-package:groupx:packagenamex, state=UNINSTALL, attributes=[org.apache.sling.installer.api.tasks.ResourceTransformer=:25:22:1170:, package-id=groupx:packagenamex:1.1.2, sph-option=INSTALL, Bundle-Version=1.1.2], digest=1111111111)
AFAICT this is a package with one subpackage (groupx:packagenamex) Cheers Dominik On Fri, Feb 17, 2017 at 1:16 PM, Karl Pauls <[email protected]> wrote: > Yeah, this is not good. I'll herby cancel this release. > > I will rollback the commit in question, reopen the original issue, and > cut a new release candidate without this change for now. > > regards, > > Karl > > On Fri, Feb 17, 2017 at 1:11 PM, Dominik Süß <[email protected]> > wrote: > > @kwin - sorry I cannot add logs as this is confidential information - > yet I > > could trace back this to the case where packages contain subpackages > which > > within the resource tranformer cause subsequent InstallTasks having the > > same URL. - This migth be a bug but needs to fixed along for this to be > > applicable. > > > > Cheers > > Dominik > > > > On Fri, Feb 17, 2017 at 1:08 PM, Konrad Windszus <[email protected]> > wrote: > > > >> Can you provide the logs? The change in SLING-6392 will always log in > case > >> it changes something (see https://svn.apache.org/viewvc/ > >> sling/trunk/installer/core/src/main/java/org/apache/ > >> sling/installer/core/impl/PersistentResourceList.java? > >> r1=1765129&r2=1783196&pathrev=1783196). So I am wondering which package > >> is actually detected as stale? > >> The according log entry should start with "Removing stale resource ..." > >> Thanks, > >> Konrad > >> > >> > On 17 Feb 2017, at 13:04, Dominik Süß <[email protected]> > wrote: > >> > > >> > Reverting to -1. Subsequential integration testing on product on top > of > >> > this did show that SLING-6392 does fail with content-packages that > >> > partially end up uninstalled instead of installed. > >> > > >> > Reverting SLING-6392 only including SLING-5457 succeeds. > >> > > >> > On Fri, Feb 17, 2017 at 1:00 PM, Stefan Seifert < > [email protected]> > >> > wrote: > >> > > >> >> +1 > >> >> > >> >> > >> > >> > > > > -- > Karl Pauls > [email protected] >
