Error Codes
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.
Status Code |
Error Codes |
Error Message |
Description |
Solution |
---|---|---|---|---|
400 |
IEF.011002 |
The API is not registered. |
The API is not registered. |
Check whether the requested URL is correct. If it is correct but the error persists, contact technical support for assistance. |
400 |
IEF.011005 |
Authentication failed. |
Authentication failed. |
Use the project ID of the tenant to obtain the token and try again. If the token is correct but the error persists, contact technical support for assistance. |
400 |
IEF.100004 |
The request offset does not comply with specifications. |
The request offset does not comply with specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100005 |
The request limit does not comply with specifications. |
The request limit does not comply with specifications. |
Locate the error cause based on the returned error information, modify the parameter value, and try again. |
400 |
IEF.100009 |
The attached volume does not meet specifications. |
The attached volume does not meet specifications. |
Enter a correct volume type. |
400 |
IEF.100010 |
The application version does not meet specifications. |
The application version does not meet specifications. |
Enter a correct application version. |
400 |
IEF.100011 |
The application template name does not comply with the specifications. |
The application template name does not comply with the specifications. |
Enter a correct application template name and try again. |
400 |
IEF.100012 |
The resource name does not comply with the specifications. |
The resource name does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100013 |
The environment variable of the application version does not comply with the specifications. |
The environment variable of the application version does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100020 |
The application icon storage URL does not meet specifications. |
The application icon storage URL does not meet specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100021 |
The description or remarks of the device binding node do not comply with the specifications. |
The description or remarks of the device binding node do not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100040 |
Invalid image path |
Invalid image path |
Enter a correct image path and try again. |
400 |
IEF.100047 |
The application template visualization parameter type is not supported. |
The application template visualization parameter type is not supported. |
Correctly set the parameter. The template visualization property value can only be public, private, shared, or left empty. |
400 |
IEF.100057 |
Device should not exist at the same time. |
The device is in both addition and deletion lists. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100058 |
The device has been bound to a node. |
The device has been bound to a node. |
Unbind the device from the node and then delete the device. |
400 |
IEF.100065 |
The system subscription ID does not meet requirements. |
The system subscription ID does not meet requirements. |
Correctly set the message subject according to the API Reference and try again. |
400 |
IEF.100067 |
The node cannot be deleted because it has bound devices. |
The node cannot be deleted because it has bound devices. |
Log in to the IEF console, go to the Edge Nodes page, click the target node to open its node details page, and check whether the node has any bound devices. If yes, unbind the devices from the node and try again. |
400 |
IEF.100100 |
The request parameter is incorrect. |
The request parameter is incorrect. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100103 |
Node group cert quota exceed. |
Node group certificates exceed quota. |
Change the parameter value based on the error cause described in the response body, ensure that the quota is sufficient, and try again. |
400 |
IEF.100112 |
The configmap/secret of the mounted volume is incorrect. |
The configmap/secret of the mounted volume is incorrect. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100113 |
The resource configuration of the application version does not comply with the specifications. |
The resource configuration of the application version does not comply with the specifications. |
Enter correct resource configuration for the application version. |
400 |
IEF.100119 |
The name of the application configuration item does not comply with the specifications. |
The name of the application configuration item does not comply with the specifications. |
Enter a correct ConfigMap name. |
400 |
IEF.100120 |
The key of the application configuration item does not comply with the specifications. |
The key of the application configuration item does not comply with the specifications. |
Enter a correct key for the ConfigMap. |
400 |
IEF.100121 |
The value of the application configuration item does not meet the specifications. |
The value of the application configuration item does not meet the specifications. |
Enter a correct value for the ConfigMap. |
400 |
IEF.100122 |
The configuration data of the application configuration item does not comply with the specifications. |
The configuration data of the application configuration item does not comply with the specifications. |
Enter correct ConfigMap data. |
400 |
IEF.100126 |
Deployment quota exceeded limit. |
Insufficient resource quota |
Change the parameter value based on the error cause described in the response body to ensure that the quota is sufficient and try again. |
400 |
IEF.100129 |
Missing ID list. |
Node must be in the node list. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100130 |
Add device missing relation description. |
Parameters for adding node are missing. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100133 |
The probe configuration of the application version does not meet specifications. |
The probe configuration of the application version does not meet specifications. |
Correctly set the probe properties. Only exec, http_get, and tcp_socket_port are supported. |
400 |
IEF.100136 |
The node which the device binding is not running. |
Node not running. It cannot be changed. |
Ensure that the node is running properly and try again. |
400 |
IEF.100139 |
The number of twin of device must be lower 64. |
A single device can have up to 64 twin properties. |
Change the parameter value based on the error cause described in the response body, ensure that the quota is sufficient, and try again. |
400 |
IEF.100144 |
Device is not allowed to bind node |
Devices of this type cannot be associated. |
Ensure that the device type is correct and try again. |
400 |
IEF.100148 |
The name of the application key does not comply with the specifications. |
The name of the application key does not comply with the specifications. |
Enter a correct secret name. |
400 |
IEF.100149 |
The application key data is invalid. |
The application key data is invalid. |
Enter correct secret data. |
400 |
IEF.100150 |
The application key data type does not meet specifications. |
The application key data type does not meet specifications. |
Enter a correct secret type. |
400 |
IEF.100151 |
The application key does not comply with the specifications. |
The application key does not comply with the specifications. |
Enter a correct secret key. |
400 |
IEF.100152 |
The application key value does not meet specifications. |
The application key value does not meet specifications. |
Enter a correct secret value. |
400 |
IEF.100155 |
The key is in use and cannot be deleted. |
The key is in use and cannot be deleted. |
Stop using the secret and then delete it. |
400 |
IEF.100159 |
The application configuration item is in use and cannot be deleted. |
The application configuration item is in use and cannot be deleted. |
Stop using the ConfigMap and then delete it. |
400 |
IEF.100161 |
The node is being updated. The application cannot be deleted. |
The node is being updated. The application cannot be deleted. |
Stop updating the node and then delete the application. |
400 |
IEF.100162 |
The advanced configuration parameters of the application version do not comply with the specifications. |
The advanced configuration parameters of the application version do not comply with the specifications. |
Enter correct advanced configuration parameters for the application version. |
400 |
IEF.100163 |
The node operation type is not supported. |
The node operation type is not supported. |
Specify a correct node operation type. |
400 |
IEF.100165 |
The application key data includes at least one key-value pair. |
The application key data includes at least one key-value pair. |
Check whether at least one secret data record exists. |
400 |
IEF.100166 |
The node version is too early. The node cannot be updated. |
The node version is earlier than 2.1.5. The node cannot be updated. |
Upgrade the node to the latest version. You can view the node version and upgrade records on the node details page. |
400 |
IEF.100167 |
The node version is too early. |
Invalid application version schema |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100220 |
Device twin and its property visitor is inconsistency |
Static property of the device does not match twin property settings. |
Check the static property of the device, modify the parameter value, and try again. |
400 |
IEF.100238 |
The twin is not allowed to change. |
Invalid static property of device. It cannot be modified or deleted. |
Check the static property of the device, modify the parameter value, and try again. |
400 |
IEF.100241 |
Node is offline, could not upgrade. |
Node offline. It cannot be updated. |
Ensure that the node is running properly and try again. |
400 |
IEF.100242 |
Plugin version is not supported in such instance. |
Instance does not support add-on version. |
Ensure that the add-on version matches the instance version. Use the matching add-on version. |
400 |
IEF.100404 |
The resource does not exist. |
The resource does not exist. |
Ensure that the parameters of the requested resource are correct. If they are correct but the error persists, contact technical support for assistance. |
400 |
IEF.100406 |
This API is not support in this IEF service instance. |
Professional edition does not support this API. |
The professional edition does not support this API. Perform this operation in the enterprise edition. |
400 |
IEF.100410 |
Unmarshal failed. |
There was an error during parameter parsing. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.100412 |
Failed to query K8S cluster resources. |
Failed to query K8S cluster resources. |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.100424 |
Operation not authorized. |
Unauthorized operation. |
Ensure that the token in the request header is correct and try again. If the token is correct but the error persists, contact technical support for assistance. |
400 |
IEF.100425 |
Invalid status. |
Container abnormal. |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.100506 |
Create tag fail. |
Failed to create tag. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.101001 |
[Service Grid] Failed to convert the structure. |
[Service Grid] Failed to convert the structure. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.101002 |
[Service Grid] The service already exists. |
[Service Grid] The service already exists. |
Modify service parameters or delete unnecessary services and try again. |
400 |
IEF.101003 |
[Service Grid] The associated application does not exist. |
[Service Grid] The associated application does not exist. |
Check whether the associated application exists. Enter the correct associated application and try again. |
400 |
IEF.101004 |
[Service Grid] Failed to Create K8S Cluster Resources |
[Service Grid] Failed to Create K8S Cluster Resources |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.101005 |
[Service Grid] Failed to Delete K8S Cluster Resources |
[Service Grid] Failed to Delete K8S Cluster Resources |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.101006 |
[Service Grid] Failed to Query K8S Cluster Resources |
[Service Grid] Failed to Query K8S Cluster Resources |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.101007 |
[Service Grid] Failed to Update K8S Cluster Resources |
[Service Grid] Failed to Update K8S Cluster Resources |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.104003 |
Bad Parameter. |
There was an error during parameter verification. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.104004 |
The resource to be created already exists. |
The resource to be created already exists. |
Modify resource parameters or delete unnecessary resources and try again. |
400 |
IEF.110074 |
The specified application template cannot be found. |
The specified application template cannot be found. |
Check whether the specified application template exists. Enter the correct application template and try again. |
400 |
IEF.110076 |
The specified app version cannot be found. |
The specified app version cannot be found. |
Check whether the specified application version exists. Enter the correct application version and try again. |
400 |
IEF.110080 |
Specified device not found |
Specified device not found |
Check whether the specified device exists. Enter the correct device and try again. |
400 |
IEF.110081 |
The specified device template is not found. |
The specified device template is not found. |
Check whether the specified device template exists. Enter the correct device template and try again. |
400 |
IEF.120001 |
Internal error |
Internal error |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.300000 |
Failed to obtain request parameters. |
Failed to obtain request parameters. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300001 |
The request parameter message endpoint does not meet the requirements. |
The request parameter message endpoint does not meet the requirements. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300002 |
The name of the request parameter message endpoint does not comply with the specifications. |
The name of the request parameter message endpoint does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300003 |
The description of the request parameter message endpoint does not comply with the specifications. |
The description of the request parameter message endpoint does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300004 |
The request parameter message endpoint type is not supported. |
The request parameter message endpoint type is not supported. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300005 |
The endpoint attribute of the request parameter does not comply with the specifications. |
The endpoint attribute of the request parameter does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300006 |
The request parameter message endpoint already exists. |
The request parameter message endpoint already exists. |
Change a message endpoint name, or delete the existing message endpoint without affecting services, then try again. |
400 |
IEF.300007 |
The specified message endpoint does not exist. |
The specified message endpoint does not exist. |
Check whether the specified message endpoint is deleted. Enter the correct message endpoint and try again. |
400 |
IEF.300008 |
The message endpoint is in use and cannot be deleted. |
The message endpoint is in use and cannot be deleted. |
Stop using the message endpoint or wait until the message endpoint is no longer used, and then delete the message endpoint. |
400 |
IEF.300009 |
Message Endpoint Quota Insufficient |
Message Endpoint Quota Insufficient |
Reduce the resource usage or contact technical support to increase the quota. |
400 |
IEF.300101 |
The request parameter message route does not comply with the specifications. |
The request parameter message route does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300102 |
The routing name of the request parameter does not comply with the specifications. |
The routing name of the request parameter does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300103 |
The message route description of the request parameter does not comply with the specifications. |
The message route description of the request parameter does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300104 |
The source endpoint ID of the message route does not comply with the specifications. |
The source endpoint ID of the message route does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300105 |
The source endpoint resource of the message route does not meet the specifications. |
The source endpoint resource of the message route does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300106 |
The destination endpoint ID of the message route does not comply with the specifications. |
The destination endpoint ID of the message route does not comply with the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300107 |
The destination endpoint resource of the message route does not meet the specifications. |
The destination endpoint resource of the message route does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300108 |
The specified message route already exists. |
The specified message route already exists. |
Change a message route name, or delete the existing message route without affecting services, then try again. |
400 |
IEF.300109 |
The specified message route does not exist. |
The specified message route does not exist. |
Check whether the specified message route is deleted. Enter the correct message route and try again. |
400 |
IEF.300110 |
Failed to obtain the message routing request action. |
Failed to obtain the message routing request action. |
Set the message routing action correctly and try again. |
400 |
IEF.300111 |
The message routing request action is not supported. |
The message routing request action is not supported. |
Set the message routing action correctly and try again. |
400 |
IEF.300112 |
The message route is being enabled and cannot be enabled. The message route is being disabled and cannot be disabled. |
The message route is being enabled and cannot be enabled. The message route is being disabled and cannot be disabled. |
Log in to the IEF console, locate the specified route on the Routes page, and check its status. If the route has been enabled, do not enable it again. |
400 |
IEF.300113 |
Message routing quota is insufficient. |
Message routing quota is insufficient. |
Reduce the resource usage or contact technical support to increase the quota. |
400 |
IEF.300114 |
The specified DIS channel does not exist. |
The specified DIS channel does not exist. |
Check whether the specified DIS stream is deleted. Enter the correct DIS stream and try again. |
400 |
IEF.300115 |
Invalid DIS channel requested |
Invalid DIS channel requested |
Check whether the specified DIS stream is deleted. Enter the correct DIS stream and try again. |
400 |
IEF.300116 |
The requested servicebus path does not meet specifications. |
The requested servicebus path does not meet specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300117 |
The requested eventbus topic does not meet specifications. |
The requested eventbus topic does not meet specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300118 |
The requested eventbus topic already exists. |
The requested eventbus topic already exists. |
Change an EventBus topic, or delete the existing EventBus topic without affecting services, then try again. |
400 |
IEF.300119 |
The requested APIGW resource does not meet specifications. |
The requested APIGW resource does not meet specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300120 |
The requested MQTT topic does not meet specifications. |
The requested MQTT topic does not meet specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300121 |
Duplicate MQTT topic data. |
Duplicate MQTT topic data. |
Change an MQTT topic, or delete the existing MQTT topic without affecting services, then try again. |
400 |
IEF.300122 |
The REST path of the request parameter does not meet the specifications. |
The REST path of the request parameter does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300123 |
Duplicate REST path data in the request parameter. |
Duplicate REST path data in the request parameter. |
Change a REST path, or delete the existing REST path without affecting services, then try again. |
400 |
IEF.300124 |
The request parameter device is faulty. |
The request parameter device is faulty. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
400 |
IEF.300125 |
The requested device does not exist. |
The requested device does not exist. |
Check whether the requested device is deleted. Enter the correct device and try again. |
400 |
IEF.300126 |
The requested edge node does not exist. |
The requested edge node does not exist. |
Check whether the requested edge node is deleted. Enter the correct edge node and try again. |
400 |
IEF.300127 |
The requested edge node conflicts. |
The requested edge node conflicts. |
Change an edge node, or delete the existing edge node without affecting services, then try again. |
400 |
IEF.300128 |
When the request destination port type is tsdb, the projectID is empty. |
When the request destination port type is tsdb, the projectID is empty. |
Enter a correct project ID and try again. |
400 |
IEF.300129 |
When the request destination port type is tsdb, projectID is invalid. |
When the request destination port type is tsdb, projectID is invalid. |
Enter a correct project ID and try again. |
400 |
IEF.300130 |
When the request destination port type is tsdb, domain_id is invalid. |
When the request destination port type is tsdb, domain_id is invalid. |
Enter a correct domain ID and try again. |
400 |
IEF.300131 |
The URL is invalid when the request destination port type is tsdb. |
The URL is invalid when the request destination port type is tsdb. |
Enter a correct URL and try again. |
400 |
IEF.300132 |
When the request destination port type is tsdb, the label is invalid. |
When the request destination port type is tsdb, the label is invalid. |
Enter a correct tag and try again. |
400 |
IEF.300133 |
The requested edge node does not exist. |
The requested edge node does not exist. |
Check whether the requested edge node is deleted. Enter the correct edge node and try again. |
400 |
IEF.300134 |
When the request destination port type is tsdb, the resource does not meet the specifications. |
When the request destination port type is tsdb, the resource does not meet the specifications. |
Enter a correct resource and try again. |
400 |
IEF.300135 |
The nodeId is empty or does not comply with the specifications. |
The nodeId is empty or does not comply with the specifications. |
Enter a correct node ID and try again. |
400 |
IEF.300201 |
The quota type is incorrect. |
The quota type is incorrect. |
Change the quota type based on the returned error information or the API Reference and try again. |
400 |
IEF.310000 |
The request does not contain a token. |
The request does not contain a token. |
Ensure that the request header contains the correct token. |
400 |
IEF.310001 |
Failed to obtain the token in the request. |
Failed to obtain the token in the request. |
Ensure that the entered token is correct or obtain a new token. If the token is correct but the error persists, contact technical support for assistance. |
400 |
IEF.310002 |
The token has expired. |
The token has expired. |
Obtain a new token. |
400 |
IEF.310003 |
Failed to connect to the database. |
Failed to connect to the database. |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.330000 |
Failed to connect to the DIS service. |
Failed to connect to the DIS service. |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.330001 |
Failed to connect to the edgebroker. |
Failed to connect to the edgebroker. |
An internal error occurred. Contact technical support for assistance. |
400 |
IEF.340000 |
Failed to convert the token. |
Failed to convert the token. |
Ensure that the token is correct or contact technical support for assistance. |
400 |
IEF.340001 |
Internal error |
Internal error |
An internal error occurred. Contact technical support for assistance. |
401 |
IEF.100049 |
ProjectID is not match this token. |
Project ID does not match token. |
Obtain the token using the project ID of the tenant and try again. If the token is correct but the error persists, contact technical support for assistance. |
401 |
IEF.100050 |
Invalid certificate. |
Token authentication failed. |
Ensure that the token in the request header is correct and try again. If the token is correct but the error persists, contact technical support for assistance. |
401 |
IEF.110001 |
The auth token is not found. |
Token not found. |
Ensure that the token in the request header is correct and try again. If the token is correct but the error persists, contact technical support for assistance. |
401 |
IEF.110002 |
Bad token. |
Invalid token. |
Ensure that the token in the request header is correct and try again. If the token is correct but the error persists, contact technical support for assistance. |
403 |
IEF.100401 |
No running node in group. |
No node running in node group. |
No node is running in the node group. Start the node and try again. |
403 |
IEF.130087 |
Deployment is pending create. |
The Deployment is being created. |
The Deployment is being created and cannot be deleted. |
404 |
IEF.100109 |
Resource not found. |
Specified resource not found. |
The specified resource does not exist. Ensure that the resource status is normal and try again. |
404 |
IEF.100173 |
Edge node not found. |
Empty node list. |
Manage the node and try again. |
404 |
IEF.110085 |
DeviceAccessConfig of devcice not found. |
Device configuration not found. |
The device configuration is missing. Reconfigure the device. |
409 |
IEF.100117 |
Deployment is being deleted. |
The Deployment is being deleted. |
The Deployment is being deleted. Do not delete it again. |
409 |
IEF.100172 |
Node is not running. |
Node not running. |
Ensure that the node is running properly and try again. |
409 |
IEF.130085 |
Duplicated key in tags. |
Duplicate tag keys. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
409 |
IEF.130086 |
Resource existed. |
Resource already exists. |
Check whether the resource is added repeatedly and try again. |
409 |
IEF.130091 |
Instance is existed do not allow to delete. |
Node associated with an instance or Deployment. It cannot be deleted. |
Delete the instance or Deployment associated with the node and try again. |
500 |
IEF.100411 |
k8s client failed. |
Failed to request Kubernetes cluster. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100413 |
Update k8s failed. |
Failed to update Kubernetes cluster resource. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100414 |
Delete k8s failed. |
Failed to delete Kubernetes cluster resource. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100415 |
Create k8s failed. |
Failed to create Kubernetes cluster resource. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100417 |
Failed to create ief instance. |
Failed to create cluster. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100418 |
Failed to refresh token. |
Failed to update authentication information. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100419 |
Failed to delete ief instance. |
Failed to delete cluster. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100426 |
Data struct error. |
Data abnormal. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100427 |
Internal error. |
Internal error. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100428 |
Operation error. |
Operation error. |
An internal error occurred. Contact technical support for assistance. |
500 |
IEF.100429 |
Operation error. |
Operation error. |
An internal error occurred. Contact technical support for assistance. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot