Redeploying module with resource actions XML doesn't refresh portlet permissions

• Type: Bug
• Status: Verified
• Resolution: Unresolved
• Affects Version/s: 7.0.X, 7.1.X, Master
• Fix Version/s: None
• Component/s: Core Infrastructure > Permissions
• Labels:
  • 7.3-known-issues
  • 7.4-known-issues
  • fc_19_07
  • liferay-ga1-ce-740
  • liferay-ga1-dxp-7413
  • liferay-ga10-ce-743
  • liferay-ga11-ce-743
  • liferay-ga12-ce-743
  • liferay-ga13-ce-743-known-issue
  • liferay-ga14-ce-743-known-issues
  • liferay-ga15-ce-743-known-issues
  • liferay-ga16-ce-743-known-issues
  • liferay-ga17-ce-743-known-issues
  • liferay-ga18-ce-743-known-issues
  • liferay-ga19-ce-743-known-issues
  • liferay-ga2-ce-741
  • liferay-ga20-ce-743-known-issues
  • liferay-ga21-ce-743-known-issues
  • liferay-ga22-ce-743-known-issues
  • liferay-ga23-ce-743-known-issues
  • liferay-ga24-ce-743-known-issues
  • liferay-ga4-ce-733
  • liferay-ga4-ce-743
  • liferay-ga5-ce-734
  • liferay-ga5-ce-743
  • liferay-ga6-ce-735
  • liferay-ga6-ce-743
  • liferay-ga7-ce-736
  • liferay-ga7-ce-743
  • liferay-ga8-ce-737
  • liferay-ga8-ce-743
  • liferay-ga9-ce-743
  • liferay-u1-dxp-7413
  • liferay-u2-dxp-7413
• Fix Priority: 4
• Sprint: AS | Iteration 9, AS | Iteration 10, AS | Iteration 11, AS | Iteration 12, AS | Iteration 13, AS | Iteration 14, AS | Iteration 15, AS | Iteration 16, AS | Iteration 17, AS | Iteration 18, AS | Iteration 19, AS | Iteration 20, AS | Iteration 21
• Git Pull Request: https://github.com/Preston-Crary/liferay-portal/pull/629

Problem description:

When a portlet is made up only of {{MVCAction}}s it doesn't need to depend on other services / components. For example it doesn't depend on *-service module that contributes to portlet resource actions. When such contributing module is redeployed with resource action changes those changes are not reflected in resource permissions.

 

Steps to reproduce:

1. Stop portal if running
2. Clean portal database
3. Comment out resource.actions.configs in oauth2-provider-service/portlet.properties
4. Build and deploy oauth2-provider-service module
5. Start portal
6. Go to Control Panel -> OAuth 2 Administration
7. Verify there are error logs similar to
   com.liferay.portal.kernel.exception.NoSuchResourcePermissionException: {companyId=20100, name=com.liferay.oauth2.provider, primKey=com.liferay.oauth2.provider, scope=4}
8. Undo changes in oauth2-provider-service/portlet.properties
9. Build and deploy oauth2-provider-service module
10. Wait for module deployment and visit again Control Panel -> OAuth 2 Administration

 Expected result: No error in logs
 Actual result: Again the same error log