The customer environment is the upgrade of FusionCloud 2.06 to FusionCloud 6.3.0. The customer works normally before upgrading, and the VDC created after the upgrade is used to apply for ECS.
1. Check the quota resources of the VDC and find that it is sufficient, and the comparison with the underlying resources is sufficient.
2, according to the HTTPS code request analysis, the bottom layer does not check the resources but the direct feedback resources are not available
According to the code analysis, it is found that the quota of the version of FusionCloud 2.06 before the upgrade operation is performed by the underlying openstack. The FusionCloud 6.3.0 version is audited by the MO side, and the corresponding parameters are not adjusted after the upgrade.
You need to log in to the control node and import environment variables.
1, query gaussdb master node, cps template-instance-list --service gaussdb gaussdb
2. Log in to the master node and switch to the gaussdba user, su - gaussdba
3. Perform database parameter modification operations.
A, modify the parameters of the cinder: gsql -d cinder -W FusionSphere123 -c "update QUOTAS set HARD_LIMIT='-1';"
B. Modify the parameters of nova: gsql -d nova -W FusionSphere123 -c "update QUOTAS set HARD_LIMIT='-1';"
Note: Be cautious and need to be confirmed again and again.
For upgraded products, there are some architectural changes that require careful review of every detail.