Oracle 云计划变更(2026-5-12)
🇺🇸原文:
Oracle Cloud Infrastructure Block Volumes - Service Update: Limit and Quota Enforcement
Oracle Cloud Infrastructure Customer,
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.
🇨🇳中文翻译:
Oracle 云基础设施块存储卷 - 服务更新：限制和配额执行
Oracle 云基础设施客户
Oracle 云基础设施 (OCI) 块卷服务现在在计算实例启动期间创建启动卷时，会强制执行租户级别的total_storage_gb 限制和区间配额。
此前，这些限制和配额并未在此特定工作流程中进行验证，因此即使超过了配置的限制或配额阈值，某些实例启动仍可创建启动卷。
通过此次更新，OCI 会在实例启动期间创建启动卷之前验证适用的限制和配额。如果所需的启动卷容量超过租户限制或区间配额，则实例启动将失败，并出现限制或配额错误。
为了最大限度地减少干扰，Oracle 会在必要时主动调整受影响租户的容量限制，然后再强制执行。
这一变化：
不影响现有启动卷、块卷或正在运行的实例
仅适用于启用强制执行后启动的新实例或创建新启动卷的工作流。
常见问题解答
我可以申请重新安排时间或选择不进行此次变更吗？ 不。这是块卷服务版本中包含的计划服务行为强制执行措施，无法推迟。
如果遇到故障该怎么办？ 如果实例启动因限制或配额而失败，请提交 OCI 支持请求或联系您的客户团队。请提供以下详细信息：
租户 OCID
区域和可用性域 (AD)
隔室 OCID
请求时间戳
错误信息和请求 ID（如有）
所需操作
客户应在部署实例前主动审查并调整块存储卷限制和区间配额。由于这些检查现在会在实例启动期间强制执行，容量不足可能会导致配置失败。
