How to debug when mission control can't deploy plugins to artifactory

How to debug when mission control can't deploy plugins to artifactory

AuthorFullName__c
Paul Pan
articleNumber
000004860
ft:sourceType
Salesforce
FirstPublishedDate
2021-02-01T22:35:58Z
lastModifiedDate
2023-01-22T11:08:13Z
VersionNumber
5

 

  1. Check if all plugins are deployed to artifactory. You can easily verify this in artifactory request logs and you can run the plugin api or check the plugin folders to verify we have all plugins.

  GET /api/plugins

  If you don't see it in logs, or if artifactory failed to load any plugins, you could try to deploy them manually.

  2. If Artifactory does have all plugins, and you are still seeing an error, it's likely due to the following api call failed:

  GET /api/plugins/execution

  3. In rare situation, the above api calls might get blocked by firewalls, and as an results you won't see the above api call in artifactory request logs. 

 

One known case is with IBM Spectrum, some default rules could block the call to /api/plugins/execution and you won't even see it in reverse proxy logs. Only solution in such case is to unblock to rules. 
User-added image