In the OSGi lifecycle, a bundle goes through states: Installed - > Resolved - > Active. A bundle remains stuck in the "Installed" state when the OSGi framework cannot resolve its dependencies—specifically, the Java packages listed in its Import-Package manifest header. If a required dependency is missing from the container, the bundle cannot transition to "Resolved". Issues inside the actual components (like exceptions during @Activate, missing configs, or unsatisfied @Reference annotations) will allow the bundle itself to become "Active", but the specific component will remain unsatisfied.