Hello, everyone!
VDC operations are abnormal. The possible causes are as follows:
Failed to delete the VDC. The system displays a message indicating that resources are occupied, the VDC list fails to be exported, the administrator cannot cancel the release, the quota cannot be set, the project fails to be created, and the project cannot be associated with the region.
1. Failed to Delete a VDC on the ManageOne Operation Plane
a. The error message "Failed to delete the approval process in the VDC" is displayed when a VDC is deleted on the ManageOne operation plane.
b. The environment is migrated from an earlier version. When deleting a VDC on the ManageOne 6.3.1 ServiceCenter, the system checks the VDC ID length. If the length is not 36, an error is reported and the deletion fails. This problem will be resolved in ManageOne 6.3.1.SPH1.
Solution: The standard action is to upgrade the current version to ManageOne 6.3.1.SPH1 or later.
2. Failed to Delete a VDC on the ServiceCenter
The VDC fails to be deleted on the SC page, and a message is displayed indicating that resources are occupied. If the project fails to be deleted, a message is displayed indicating that resources are occupied. For details, see the case The VDC cannot be deleted, and a message indicating that resources are occupied is displayed.
3. Failed to Delete a Tenant on ManageOne 6.3.x
A VDC administrator is included in the tenant to be deleted.
Solution: Delete the user under the tenant, log in to the operation plane as an administrator, and delete the tenant. The deletion is successful.
Note: When deleting a first-level VDC (tenant) as an operation administrator, ensure that the number of lower-level VDCs is 0, the number of users is 0, the number of projects associated with resources is 0, the number of customized roles is 0, and the number of user groups is 0.
4. Failed to Upload Files to the Server
The VDC list failed to be exported on the ManageOne operation plane. A message "Failed to upload files to the server" is displayed on the task center.
For details, see the case Failed to export the VDC list. The message "Failed to upload the file to the server" is displayed.
5. Failed to set quotas for second-level VDCs
Failed to set quotas for second-level VDCs on the ManageOne operation plane.
Troubleshooting Procedure
a. Log in to the ManageOne operation plane as the bss_admin user, choose Tenant > Tenant Management, and search for the tenant name (first-level VDC name).
b. Go to the quota information page, click Quota Management, and check the quota allocation of the tenant (first-level VDC)
The Current-Level Quota of the tenant (first-level VDC) is equal to the Total Quota.
Root Cause
The Current-Level Quota of the tenant (first-level VDC) is equal to the Total Quota. As a result, no quota can be set for second-level VDCs.
Solution
Adjust the current-level quota of a tenant (first-level VDC). Ensure that the current-level quota of a tenant is less than the total quota, quotas can be set for second-level VDCs.
6. Failed to Associate a Project with a Region
The project cannot be associated with a region. If the VDC quota is disassociated with a region and then associated with a region on ManageOne 6.3.1, the project cannot be associated with the region.
For details, see the case Failed to Associate a Project with a Region.
That's all, thanks!
