VMware Cloud Director Object Storage Extension 2.2.0.1 | 22 DEC 2022 | Build 20989128

Check for additions and updates to these release notes.

What's New

VMware Cloud Director Object Storage Extension version 2.2.0.1 provides the following new capabilities:

  • Improvement on the support for Object Storage Interoperability Service (OSIS), including IAM user support, tenant onboard and bucket synchronization.

  • Various bug fixes.

Upgrade

You can upgrade directly to VMware Cloud Director Object Storage Extension 2.2.0.1 from versions 2.2 and 2.1.X. See Upgrading VMware Cloud Director Object Storage Extension.

Caveats and Limitations

  • S3 API requests authenticated with application credentials do not support the following use cases:

    • Accessing a shared bucket if another user grants you permissions for the bucket.

    • Deleting multiple objects simultaneously with a single API request.

    • Copying objects from buckets that you own.

  • If you are using ECS storage, you cannot remove object tags.

    When you try to remove an object tag, the operation fails with an error.

  • VMware Cloud Director and the underlying storage systems have different limitations on user names. To use VMware Cloud Director Object Storage Extension, user names must comply with both the requirements of VMware Cloud Director and the underlying storage system. A best practice is to use short user names (under 50 bytes) and to use alphanumeric characters.

    • If you are using Cloudian storage, the maximum length of user IDs is 255 bytes.

    • If you are using Dell ECS 3.4 or earlier, the maximum length of user IDs is 91 bytes.

    • If you are using Dell ECS 3.6, the maximum length of user IDs is 64 bytes.

  • Bucket synchronization supports up to 10 million objects per a single synchronization job

    When the cloud provider enables bucket synchronization for a tenant in the provider portal, the synchronization can support up to 10 million objects for the tenant. VMware Cloud Director Object Storage Extension 2.1 does not support the synchronization for more than 10 million objects per a single bucket synchronization job.

  • If you are using ECS storage, S3 API, or the Find a Bucket feature, you cannot visit a bucket that belongs to a different tenant organization in the ECS platform.

Product Documentation

All documentation is available on the VMware Cloud Director Object Storage Extension Documentation page.

Resolved Issues

  • NEW Head Object S3 API does not return actual Content-Length header

    If the S3 client uses a HEAD method on an object, the response returns Content-Length as 0, although the object is not empty.

    This issue is now fixed.

  • NEW You cannot onboard a tenant organization for the Cloudian platform

    When a cloud provider tries to enable a tenant organizatioin for Cloudian object storage, the process fails. The problem is observed for new organizations, which have not been previously onboarded and have no custom storage mapping.

    This issue is now fixed.

  • NEW You cannot delete Kubernetes clusters, which are in fatal state

    When a tenant user tries to remove a Kubernetes cluster which is in fatal state, the process fails. The problem is observed only with Kubernetes clusters, which are added to Object Storage Extension 2.1.

    This issue is now fixed.

Known Issues

  • You cannot log in to VMware Cloud Director Object Storage Extension as a service administrator

    When you try to log in to VMware Cloud Director Object Storage Extension as a service administrator, the login is unsuccessful. The problem is observed on a random basis and it occurs if you have multiple groups which are mapped to multiple VMware Cloud Director roles.

    Workaround: Log in to VMware Cloud Director Object Storage Extension with a user that has a single group, mapped to their VMware Cloud Director role.

  • Bucket synchronization does not synchronize all objects when object paths contain special symbols

    VMware Cloud Director Object Storage Extension synchronizes the first 1,000 objects to the database. Special symbols include characters that might be encoded in the URL.

    Workaround: None.

  • You cannot push images to the VMware Harbor Registry

    When you try to push an image to the VMware Harbor Registry and the VMware Harbor Registry server uses VMware Cloud Director Object Storage Extension S3 as a backend storage, the process fails. The problem is observed when VMware Harbor Registry is configured with VMware Cloud Director Object Storage Extension S3 endpoint and credentials.

    Workaround: Request a hotfix from VMware.

  • You cannot create a bucket policy with a UI-generated service instance ID

    When you try to create a bucket policy and use the UI to generate the service instance ID, the process fails.

    Workaround: Create the service instance ID manually and ensure it does not include the hyphen symbol (-) .

  • The S3 service of VMware Cloud Object Storage Extension is unavailable

    When you start or view VMware Cloud Object Storage Extension, the VMware Cloud Object Storage Extension service is active, but the S3 service is unavailable, with the following error message in the log file:

    S3_TOKEN_AUTH_ERROR

    The issue is observed if the time gap between the S3 client and the VMware Cloud Object Storage Extension VM is over 20 seconds. 

    Workaround 1: Change the gap time between the S3 client and the VMware Cloud Object Storage Extension VM to less than 20 seconds, for example, NTP for the VMware Cloud Object Storage Extension VM.

    Workaround 2: Run the command oss.s3.request-expire-time=3600 and restart the VMware Cloud Object Storage Extension service.

  • Synchronization tasks of buckets with more than 60 thousand objects fail with a timeout error

    When you try to sync a bucket that contains more than 60 thousand objects, the synchronization task expires after 24 hours.

    Workaround: Click the Sync Now button repeatedly until the synchronization task completes successfully.

  • Region metrics on the provider portal's tenant onboarding page does not distinguish region specific metrics data

    With multi-region deployment, when multiple regions are activated for a tenant organization, active region cards show the global consumption metrics, not region-specific data. The problem is observed, because region specific metrics is not supported yet.

    Workaround: None.

check-circle-line exclamation-circle-line close-line
Scroll to top icon