Updated on 2022-09-26 GMT+08:00

General Checks

Symptom

A BCS instance fails to be purchased.

Solution

  • Check item 1: Check whether the account is in arrears.
    1. Log in to the BCS console and click Billing Center in the upper part of the page.

      If Account Balance is zero or less than the price displayed when you purchase the BCS instance, the purchase will fail.

    2. In the Pending Orders area, click Pay Now. On the Orders page that is displayed, select the order to be paid and complete the payment.

      If the payment fails and a message is displayed indicating that the balance is insufficient, the purchase will also fail.

    3. In the Pending Renewal area, click View All. On the displayed page, select the resources to be renewed and click Renew.
  • Check item 2: Check whether the permissions of the IAM user are insufficient.

    If the instance is purchased by using an IAM user, obtain permissions by following instructions in Permissions Management.

  • Check item 3: Check the details error information.
    1. Log in to the BCS console. In the navigation pane, click Instance Management.
    2. Click Task Details on the right.
    3. Click View Details in the Operation column.
    4. In the displayed window, click View Cause to analyze the failure. For details, see Table 1.
    Table 1 Errors and solutions

    Error

    Solution

    Insufficient cluster quota

    CCE Cluster Quota Used Up

    CreateContainerCluster] Create Cluster fail

    Failed to Create a Cluster

    CreateStorageInstance]Create PVC fail,timeout

    Failed to Create a PVC

    CreateBlockchainService]cluster is already used

    Cluster Already In Use

    CreateStorageInstance] PostReqNoCert: response status 400 not OK, resp is: {"errCode":"SFS.TURBO.0010","errMsg":"instance quota exceeds"}

    SFS Turbo File System Quota Exceeded

    not find down eip, need buy one

    No EIP Bound

    CreateContainerCluster]visitInterface Fail,/api/v2/projects/xxx/clusters response state not OK,code:500

    CCE Is Abnormal

    CreateBlockchainService]DeleteKubeResource failed, clusterID:xxx, resourceName: xxx, err:DELETE:response status 400 not OK, resp is:Cluster Status Not Ready

    Cluster Status Is Abnormal

    CreateContainerCluster]Invalid subnet id xxx

    Subnet Unavailable

    CreateBlockchainService]one OneStep is processing under this domain(xxx),please wait it finished and do it again

    Quick Deployment in Progress

    CreateContainerCluster]cce status check timeout when checkClusterJobStatus...

    CCE Status Check Times Out

    CreateContainerCluster] VisitInterface Fail, PostReqNoCert: response status 400 not OK, resp is: {"message":"\u003cCCE_CM.4000311\u003e No available master flavors | The amount of available master flavors are not enough to create a cluster, in specified azs, need 1, has 0","reason":"BadRequest","code":400}

    Insufficient Master Nodes in the AZ of the CCE Cluster