| | | |
400 | InvalidApplication.NotFound
| The current application does not exist. | 诊断 |
400 | InvalidParameter.NotEmpty
| You must specify the parameter %s. | 诊断 |
400 | InvalidParameter.Obviously
| The specified parameter is invalid {%s}. | 诊断 |
400 | InvalidParameter.WithMessage
| The parameter is invalid {%s}: %s | 诊断 |
400 | NoComputeResourceQuota.Exceed
| Your compute resource is insufficient. Please contact us to raise the quota. | 诊断 |
400 | | The user has an outstanding payment. | 诊断 |
400 | NoComputeResourceQuota.App.Exceed
| You can create %s instances for each application. Please submit a ticket to raise the quota. | 诊断 |
400 | NoComputeResourceQuota.User.Exceed
| Your account is limited to create %s instances. Please submit a ticket to raise the quota. | 诊断 |
400 | | The system is being upgraded. Please try again later. | 诊断 |
400 | Application.ChangerOrderRunning
| An application change process is in progress. Please try again later. | 诊断 |
400 | Application.InvalidStatus
| The application status is abnormal. Please try again later. | 诊断 |
400 | | The application has not been deployed. Please deploy it and try again. | 诊断 |
400 | | Failed to roll back. | 诊断 |
400 | | Your application must at least contain a JDK component. | 诊断 |
400 | JarApplication.MissingJdk
| A FatJar application must contain JDK. | 诊断 |
400 | PandoraApplication.MissingJdk
| The Pandora application is missing a JDK component. | 诊断 |
400 | WarApplication.MissingJdkWebcontainer
| A War application must contain JDK and Tomcat. | 诊断 |
400 | InvalidComponent.NotFound
| The current component (such as JDK, Tomcat, or EDASWebContainer) does not exist. | 诊断 |
400 | InvalidHostnameIp.Invalid
| The hostname and/or IP is invalid: Hostname [%s], IP [%s]. | 诊断 |
400 | InvalidInstanceSpecification.Unsupported
| The instance specification is not supported: CPU [%s], memory [%s]. | 诊断 |
400 | InvalidPackageType.NotFound
| The package type must be War, FatJar, or Image. | 诊断 |
400 | LogService.ConfigQuotaExceed
| The maximum number of Log Service configs is exceeded. | 诊断 |
400 | | An exception occurred while calling Log Service. Please submit a ticket to solve the problem. | 诊断 |
400 | | The log collection path is invalid. | 诊断 |
400 | | Log Service is unavailable. Please activate Log Service first. | 诊断 |
400 | LogService.ProjectNumQuotaExceed
| The maximum number of Log Service projects is exceeded. | 诊断 |
400 | | Conflict between log collection directory and persistent storage directory. | 诊断 |
400 | | Conflict detected for ConfigMap path %s. | 诊断 |
400 | | The ConfigMap object (ID: %s) does not exist. | 诊断 |
400 | | The key %s of ConfigMap object (ID: %s) does not exist. | 诊断 |
400 | MinReadyInstances.Not.Smaller.Replicas
| The minimum number of available instances must be less than the number of application instances. | 诊断 |
400 | MinReadyInstanceRatio.Invalid
| The ratio of minimum available instances must be between 0 and 100. | 诊断 |
400 | | The maximum length of package version is exceeded. | 诊断 |
400 | App.Package.Version.Exists
| The package version of application already exists. | 诊断 |
400 | | The SLB instance is occupied. | 诊断 |
400 | | The current SLB instance cannot be reused because it may have been occupied by %s. | 诊断 |
400 | InvalidParameter.FileName
| The application deployment package name is invalid. This name can contain only alphanumeric characters, hyphens (-), and underscores (_). For deploying java package, you can upload JAR files only if the selected deployment version supports JAR file. Otherwise, upload WAR files only. For deploying php package, you can upload ZIP files only if the selected deployment version supports ZIP file. | 诊断 |
400 | | The specified vSwitch does not exist. | 诊断 |
404 | InvalidNamespaceId.NotFound
| The specified NamespaceId does not exist. | 诊断 |