Why does my PVC stay in Pending status when using capacity roundoff?

Virtual Private Cloud

Your PVC stays in Pending status and you see a ProvisioningFailed warning event when using a StorageClass with allowCapacityRoundoffForIops: "true" enabled.

One of the following conditions might be causing the failure:

  • The driver could not reach IBM Global Catalog at startup and the DP2 catalog was not loaded. Capacity roundoff requires the driver to fetch a supported capacity-to-IOPS catalog from Global Catalog during startup.
  • The requested IOPS or capacity combination is not valid for the dp2 profile.

Check the PVC events to identify the error message, then resolve the issue based on the following table.

  1. Run the following command and look for a Warning event with a ProvisioningFailed reason.

    oc describe pvc PVC_NAME

  2. Match the error message to the resolution in the following table.

Common capacity roundoff provisioning failures
Error message in events Cause Resolution
capacity round-off is unavailable because the DP2 catalog could not be loaded during driver startup The driver could not reach Global Catalog at startup. Verify that your Virtual Private Endpoint Gateway (VPEG) is configured correctly and that the driver can reach private.globalcatalog.cloud.ibm.com. Restart the driver pods after fixing connectivity. For setup instructions, see Prerequisites.
shares_profile_capacity_iops_invalid The requested IOPS or capacity combination is not valid for the dp2 profile. Check that the requested IOPS is within the supported range for the dp2 profile and that the requested capacity does not exceed the profile maximum.