OTK components in Manage Solution Kits window appear to be missing after trying to install new components

book

Article ID: 141589

calendar_today

Updated On:

Products

CA API Gateway API SECURITY STARTER PACK-7 CA Microgateway

Issue/Introduction

When running an "upgrade" instead of an "install" to add a new component to an existing OAuth Solution Kit via the Manage Solution Kits function, other already-installed components will appear to be missing from the list when expanding the OAuthSolutionKit name in the Manage Solution Kits window.

The services still exist and there should be no noticeable impact to the environment, this is more of a GUI issue.

Example of instructions followed which could lead to this issue if "upgrade" is used instead of "install" for any new components: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-management-oauth-toolkit/4-3/installation-workflow/install-the-oauth-solution-kit/install-otk-with-api-portal-integration.html

Cause

This is caused by running an "upgrade" to install a new component when the "install" option should have been used for that task instead.

Environment

This may happen in any version of Policy Manager / Gateway / OTK solution kit.

Resolution

The only option to get back to normal is to restore from a backup. This can be done in one of two ways:

1) Restore from a VM snapshot.
2) Restore from a backup taken using the ssgbackup.sh script prior, restoring with the ssgrestore.sh script. A full backup and restore should be done at this stage using the default restore method.

Once the Gateway is restored and running, the attempt to install the new component should be made again but this time using the appropriate "Install" method rather than "Upgrade". Do not use "Upgrade" to install new components, as that is the root cause of this behaviour in the first place. In future versions of the Gateway, this should be corrected to disallow installing new components via the "Upgrade" method.

Additional Information

Related: A known issue when restoring from a backup using ssgrestore.sh script: https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=46060