If you deploy a fragment bundle, it never changes to resolved state

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.2.10 DXP FP11, 7.2.X, Master
• Fix Version/s: 7.2.10 DXP FP12, 7.2.X, 7.3.7 CE GA8, 7.3.10 DXP FP2, 7.3.X, 7.4.0 CE GA1, 7.4.13 DXP GA1, Master
• Component/s: Core Infrastructure
• Labels:
  • NAT
  • ee-ts
  • liferay-fixpack-dxp-12-7210
  • liferay-fixpack-dxp-2-7310
• Branch Version/s:
  7.3.x, 7.2.x
• Backported to Branch:
  Committed
• Fix Priority: 4
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/100162
• Bug Type: Regression Bug

If you deploy a fragment bundle, it never changes to resolved state, it remains in "installed" state.

Steps to reproduce

1. Deploy the attached com.liferay.blade.module.jsp.override-1.0.0.jar osgi fragment module. (It was created from the blade samples)
2. Connect to the gogo shell and execute lb |grep -v Active
3. Check the state of the deployed module:
   • Expected behavior: The module is in "Resolved" status
   • Wrong behavior: The module is in "Installed" status
4. Additional verification: check that the unsolved dependency should be satisfied
   • Execute diag <bundleId> to get the missing dependency of the osgi fragment
   • Execute lb -s com.liferay.login.web to get the version of the host module
   • Verify that the fragment expects any version between 1.0.0 and 7.0.0, and the com.liferay.login.web module has a matching one.

Workaround
You can apply following steps to solve the wrong dependency:

1. Stop the application server
2. Delete the osgi/state folder content
3. Start the application server