[HCI-SCP] The operation of disabling ASEC is not correct , causing the cluster to fail to be added to SCP.

|
  • 249
  • 0

Issue Description

In some cases, where some customers had disabled the aSEC service via SCP, then deleted the cluster on SCP, when adding the cluster to SCP again it was shown as failed.

Error/Warning Information



Failed to add cluster. Failed to add or edit the cluster (192.200.X.X). Integrated authentication is established between the cluster and aSecurity. Please remove the cluster then add the cluster again!
Error Code:0x101001010019

Handling Process

1. The user first closed the aSEC service in SCP, then deleted the HCI cluster, and reported an error when adding the HCI cluster again.

2. According to the user feedback, the user did not disable the aSEC integration linkage according to the normal process.

3.Therefore, based on the current error, the integration configuration on HCI can only be manually deleted from the backend.

Root Cause

Failure to disable integration according to normal procedures, resulting in residual of authentication data.

Solution

1. Navigate to /cfs/portal-service directory. Clear the contents inside the thirdpartyservice.json file.
Note : Keep the "{ }", as the file is in json format.
vim thirdpartyservice.json
"dd" - to remove the contents of the line.

2. Same as in step 1, navigate to /cfs/authsvc/aksk/ak directory. Clear the contents in the ak.json file.
Note : Keep the "{ }", as the file is in json format.
vim ak.json

3. Attempt to add the cluster into SCP, and the cluster will be added successfully.

Suggestions

- Kindly follow the handling process and solution provided above.
- If the scenario varies from above or the solution doesn't work, kindly consult with specialist or R&D for further verification.

I want to write a case
Doc ID: 9349
Author: CTI Edward
Updated: 2023-10-06 11:49
Version: