OSGi Bundle startup issue

Try install your bundle on a fresh AEM machine using Package Manager to see if the real issue is the environment, the way you deploy (bamboo ?? - never heard of using that to deploy a package) or the package. 

Hi Scott,

     Thanks for checking issue, the same package working fine in Publisher in a vanilla instance.  We are facing this issue, since the last sprint. If its dependency issue, the publisher would have face same issue but it works fine.  

Use case, my last core bundle's build id 100 and I'm deploying the new package with #101, I can see latest package installed state without any error whereas I see bundle build id 100 in system console. After a restart, its works fine.

Wondering what went wrong, heard any similar issue before? any pointers?

Thanks Again!

Same issue we also faced it sometime back and root cause was, previous build bundle jar was locked with "root" user.

Go to this path - crx-quickstart\repository\segmentstore and see if your bundle is locked with "Root" or different user ? if yes, then you need to change the permissions using chown command if you are on Linux. 

In our case, someone started the AEM server with root permission and we had to manually update all the files which got locked with "root" user.