甲骨文发了奇怪的信息过来

Oracle Cloud Infrastructure Block Volumes - Service Update: Limit and Quota Enforcement

Oracle Cloud Infrastructure 客户,

The Oracle Cloud Infrastructure (OCI) Block Volumes service now enforces tenancy-level total_storage_gb limits and compartment quotas during boot volume creation as part of Compute instance launches.

Previously, these limits and quotas were not validated in this specific workflow, which allowed some instance launches to create boot volumes even when configured limits or quota thresholds were exceeded.

With this update, OCI validates applicable limits and quotas before creating a boot volume during instance launch. If the required boot volume capacity exceeds the tenancy limit or compartment quota, the instance launch will fail with a limit or quota error.

To minimize disruption, Oracle is proactively adjusting capacity limits for affected tenancies, where necessary, prior to enabling enforcement.

This change:

Does not impact existing boot volumes, Block Volumes, or running instances

Applies only to new instance launches or workflows that create new boot volumes after enforcement is enabled

Frequently Asked Questions
Can I request to reschedule or opt out of this change?
No. This is a planned service behavior enforcement included in a Block Volume service release and cannot be deferred.

What should I do if I encounter failures?
If an instance launch fails due to limits or quotas, open an OCI Support request or contact your account team. Include the following details:

Tenancy OCID
Region and Availability Domain (AD)
Compartment OCID
Request timestamp
Error message and request ID (if available)
Required Action
Customers should proactively review and adjust Block Volume limits and compartment quotas prior to deploying instances. Since these checks are now enforced during instance launch, insufficient capacity may result in provisioning failures.

大意是创建实例前会检查总限额（之前不检查的吗？）