terminateServerInstances

Prev Next

Overview

Terminate a server instance (VM).

Request

Request parameters

Parameter name Required Type Restrictions Description
serverInstanceNoList.N Yes List<String> It can't be duplicated. - List of the server instance numbers to be terminated
serverInstanceNo can be obtained through the getServerInstanceList action.
e.g., serverInstanceNoList.1=1088217&serverInstanceNoList.2=1021003
responseFormatType No String - Response result's format type
Options: xml | json
Default: xml

Response

Response body

Examples

Request example

GET {SERVER_API_URL}/terminateServerInstances
?serverInstanceNoList.1=1088217

Response example

<terminateServerInstancesResponse>
   <requestId>1ee84982-5712-44cb-ac99-243e59dc8eb1</requestId>
   <returnCode>0</returnCode>
   <returnMessage>success</returnMessage>
   <totalRows>1</totalRows>
   <serverInstanceList>
      <serverInstance>
         <serverInstanceNo>340843</serverInstanceNo>
         <serverName>svr-9b467c9f6c75360</serverName>
         <serverDescription />
         <cpuCount>2</cpuCount>
         <memorySize>4294967296</memorySize>
         <baseBlockStorageSize>53687091200</baseBlockStorageSize>
         <platformType>
            <code>LNX32</code>
            <codeName>Linux 32 Bit</codeName>
         </platformType>
         <loginKeyName>cloudqa</loginKeyName>
         <isFeeChargingMonitoring>false</isFeeChargingMonitoring>
         <publicIp />
         <privateIp>10.113.178.202</privateIp>
         <serverImageName>centos-6.3-32</serverImageName>
         <serverInstanceStatus>
            <code>NSTOP</code>
            <codeName>Server normal stopped state</codeName>
         </serverInstanceStatus>
         <serverInstanceOperation>
            <code>TERMT</code>
            <codeName>Server TERMINATE OP</codeName>
         </serverInstanceOperation>
         <serverInstanceStatusName>terminating</serverInstanceStatusName>
         <createDate>2017-07-27T04:08:39+0900</createDate>
         <uptime>2017-07-27T04:11:32+0900</uptime>
         <serverImageProductCode>SPSW0LINUX000032</serverImageProductCode>
         <serverProductCode>SPSVRSTAND000004</serverProductCode>
         <isProtectServerTermination>false</isProtectServerTermination>
         <portForwardingPublicIp>192.168.120.111</portForwardingPublicIp>
         <zone>
            <zoneNo>2</zoneNo>
            <zoneName>KR-1</zoneName>
            <zoneDescription>KR-1 zone</zoneDescription>
         </zone>
         <region>
            <regionNo>1</regionNo>
            <regionCode>KR</regionCode>
            <regionName>KOREA</regionName>
         </region>
         <baseBlockStorageDiskType>
            <code>NET</code>
            <codeName>Network Storage</codeName>
         </baseBlockStorageDiskType>
         <baseBlockStroageDiskDetailType>
            <code>HDD</code>
            <codeName>HDD</codeName>
         </baseBlockStroageDiskDetailType>
         <userData />
         <initScriptNo></initScriptNo>
         <accessControlGroupList>
            <accessControlGroup>
               <accessControlGroupConfigurationNo>1038</accessControlGroupConfigurationNo>
               <accessControlGroupName>ncloud-default-acg</accessControlGroupName>
               <accessControlGroupDescription>Default AccessControlGroup</accessControlGroupDescription>
               <isDefaultGroup>true</isDefaultGroup>
               <createDate>2013-12-03T10:37:39+0900</createDate>
            </accessControlGroup>
         </accessControlGroupList>
      </serverInstance>
   </serverInstanceList>
</terminateServerInstancesResponse>

Errors

Errors that may occur while using this action are listed below. For more information about common errors, see NAVER Cloud Platform API.

HTTP Response Code Return code Return message
400 10713 Not found contract information. Please check your input parameter.
400 10501 After deleting additional storage, please try again. Additional storage must be deleted by customer
400 21001 Unable to perform returning process due to set return protection. Server name : {0}
400 23006 You cannot request for server return and creation at the same time. Please make one request at a time.
400 24073 Unable to destroy the server since a public IP is associated with the server. First, please disassociate a public IP from the server. publicIpInstanceNo = {0}
400 24103 Input parameter value is invalid. The minimum length of the name is 3 bytes and the maximum, 30 bytes.
400 24105 Input parameter value is invalid. The name must contain only lower case letters, digits, and hyphen('-'); it must start with a letter and end with a letter or digit.
400 24109 The input parameter instance number is invalid.
400 24120 The input parameter server instance number is invalid.
400 25014 Unable to control the server since (other) user is currently operating storage allocated to the server.
400 25015 Unable to delete since (other) user is currently operating the server or creating server image from the server.
400 25016 Official IP is currently being allocated or deallocated to the target server. Please return the server after the task is complete.
400 25021 The settings of load balancer related to target server is currently being modified. Please return the server after the task is complete.
400 25022 Unable to return the server since (other) user is either operating target server or an error in the target server. Please confirm the status of server/ storage.
400 25023 Unable to return the server since (other) user is either operating target server or an error in default storage of the target server. Please confirm the status of server/ storage.
400 25024 Unable to return the server since (other) user is either operating target server or storage allocated to sever. Please confirm the status of server/ storage.
400 25027 You may not change since (other) user is operating the target load balance.
400 25050 (Other)Unable to operate load balancer since use is manipulating the applying server.