Procedure for deleting a storage node VM (EC2 instance) that is not included in VSP One SDS Block configuration information (AWS)

Virtual Storage Platform One SDS Block and SDS Cloud Troubleshooting Reference

Version

1.19.x

Audience

anonymous

Part Number

MK-24VSP1SDS029-04

ft:lastEdition

2026-07-06

If you are instructed to do so in the flow for troubleshooting failures, perform the procedure shown further on in this section to delete a storage node VM (EC2 instance) that is not included in VSP One SDS Block configuration information.

CAUTION:

Verify you do not use the AWS Management Console to delete the intended storage node VM. Using the AWS Management Console to delete a storage node VM might cause inconsistencies between the VM configuration file information stored in AWS and the actual resource status, resulting in abnormal maintenance operation.
If you have deleted a storage node VM by using the AWS Management Console, perform the following procedure to correct the information about a VM configuration file stored in AWS and the actual resource status.

Note on the procedure

In the following procedure, long command lines begin on a new line delimited by "\."

See Exporting configuration files Cloud for AWS in the VSP One SDS Block and SDS Cloud System Administration to obtain a configuration file from VSP One SDS Block.
Delete the AWS resources by using the configuration file that you prepared in step 1.
1. Store the set of configuration files obtained by configuration file export to the Amazon S3 bucket you specified for the templateS3Url parameter in step 1.
  
  One way to store the file in Amazon S3 is to copy the file to Amazon S3 by using the AWS CLI, for example. For details, see Example Amazon S3 operations in the VSP One SDS Cloud for AWS Setup and Configuration.
2. Run the following AWS CLI command from the controller node to create a change set.
  To do so, disable termination protection for storage nodes.
```
aws cloudformation create-change-set \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace> \
--change-set-name <any-change-set-name*> \
--template-url <Amazon-S3-URL(https)-of-VMConfigurationFile.yml> \
--include-nested-stacks \
--capabilities CAPABILITY_NAMED_IAM \
--parameters \
ParameterKey='DisableNodeTerminationProtection',ParameterValue=ALL \
ParameterKey='ConfigurationPattern',UsePreviousValue=true
```
  Note:
  * For details about the characters that can be used, see the following website.
  
  https://docs.aws.amazon.com/cli/latest/reference/cloudformation/create-change-set.html
3. Run the following AWS CLI command to view the change set (first layer).
```
aws cloudformation describe-change-set \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace> \
--change-set-name <change-set-name-specified-in-step-2-b>
```
  - Verify the following.
    - "Status" must be "CREATE_COMPLETE."
    - The number of items in "Changes" must be one.
    - "Action" must be "Modify" for "ResourceChange" of items in "Changes."
  - Note down the "ChangeSetId" value for "ResourceChange" of items in "Changes" to perform the next step.
  Note:
  If the status is "CREATE_IN_PROGRESS", wait for a while, and then retry the operation.
4. Run the following AWS CLI command to view the change set (second layer).
```
aws cloudformation describe-change-set \
--change-set-name <ChangeSetId-recorded-in-step-2-c>
```
  - Verify the following.
    - "Action" must be "Modify" for "ResourceChange" of each item in "Changes."
  - Note down the "ChangeSetId" value for "ResourceChange" of each item in "Changes" to perform the next step.
5. Run the following AWS CLI command to view the change set (third layer).
```
aws cloudformation describe-change-set \
--change-set-name <ChangeSetId-recorded-in-step-2-d>
```
  - Verify the following.
    - "Action" must be "Modify" for "ResourceChange" of each item in "Changes."
6. Run the following AWS CLI command to execute the created change set.
```
aws cloudformation execute-change-set \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace> \
--change-set-name <change-set-name-specified-in-step-2-b>
```
7. Run the following AWS CLI command to verify the execution results of the change set.
  - Run the "wait stack-update-complete" command. You can wait until the change-set execution completes.
```
aws cloudformation wait stack-update-complete \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace>
```
  - After "wait stack-update-complete" completes, run the "describe-stacks" command to verify that "StackStatus" is "UPDATE_COMPLETE."
```
aws cloudformation describe-stacks \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace>
```
8. Run the following AWS CLI command to create a change set.
```
aws cloudformation create-change-set \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace> \
--change-set-name <any-change-set-name*> \
--use-previous-template \
--include-nested-stacks \
--capabilities CAPABILITY_NAMED_IAM
```
  Note:
  * For details about the characters that can be used, see the following website.
  
  https://docs.aws.amazon.com/cli/latest/reference/cloudformation/create-change-set.html
9. Run the following AWS CLI command to view the change set (first layer).
```
aws cloudformation describe-change-set \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace> \
--change-set-name <change-set-name-specified-in-step-2-h>
```
  - Verify the following.
    - "Status" must be "CREATE_COMPLETE."
    - The number of items in "Changes" must be one.
    - "Action" must be "Modify" for "ResourceChange" of items in "Changes."
  - Note down the "ChangeSetId" value for "ResourceChange" of items in "Changes" to perform the next step.
  Note:
  If the status is "CREATE_IN_PROGRESS", wait for a while, and then retry the operation.
10. Run the following AWS CLI command to view the change set (second layer).
```
aws cloudformation describe-change-set \
--change-set-name <ChangeSetId-recorded-in-step-2-i>
```
  - Verify the following.
    - "LogicalResourceId" of the items whose "Action" is "Remove" must be "StorageNodeXX" or "SpgYY" for "ResourceChange" of each item in "Changes."
      
      (XX indicates the storage node number to be deleted and YY indicates the number of the spread placement group to which the storage node to be deleted belongs.)
    - "Action" must be "Modify" for "ResourceChange" of each item in "Changes" except the preceding cases.
  - Note down the "ChangeSetId" value for "ResourceChange" of each item in "Changes" to perform the next step.
11. Run the following AWS CLI command to view the change set (third layer).
```
aws cloudformation describe-change-set \
--change-set-name <ChangeSetId-recorded-in-step-2-j>
```
  - Verify the following.
    - "LogicalResourceId" of the items whose "Action" is "Remove" must be "ComputeNetworkXX", "ControlNetworkXX" or "InterNodeNetworkXX" for "ResourceChange" of each item in "Changes."
      
      (XX indicates the storage node number to be deleted.)
    - "Action" must be "Modify" for "ResourceChange" of each item in "Changes" except the preceding cases.
12. Run the following AWS CLI command to execute the created change set.
```
aws cloudformation execute-change-set \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace> \
--change-set-name <change-set-name-specified-in-step-2-h>
```
13. Run the following AWS CLI command to verify the execution results of the change set.
  - Run the "wait stack-update-complete" command. You can wait until the change-set execution completes.
```
aws cloudformation wait stack-update-complete \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace>
```
  - After "wait stack-update-complete" completes, run the "describe-stacks" command to verify that "StackStatus" is "UPDATE_COMPLETE."
```
aws cloudformation describe-stacks \
--stack-name <stack-name-set-at-the-time-of-installation-from-AWS-Marketplace>
```