RSS
 

VMware Cloud Director Object Storage Extension 2.1.1.1 | 23 JUN 2022 | Build 19993560

Check for additions and updates to these release notes.

What's New

This release of VMware Cloud Director Object Storage Extension includes bug fixes and the following new features:

  • Usage reporting for Cloudian

Starting with VMware Cloud Director Object Storage Extension 2.1.1.1, cloud providers can retrieve usage reports for their organizations. Using API calls, cloud providers can set the usage report granularity to an hourly, a daily, or a monthly basis, and also specify the start and the end date of the report. This feature is only available for the Cloudian platform.

  • Billing capability for Cloudian

VMware Cloud Director Object Storage Extension 2.1.1.1 introduces a billing functionality. Using API calls, cloud providers can retrieve billing information for a specific organization. This feature is only available for the Cloudian platform.

Upgrade

You can upgrade directly to VMware Cloud Director Object Storage Extension 2.1.1.1 from versions 2.1.1, 2.1, and 2.0. See Upgrading VMware Cloud Director Object Storage Extension.

Resolved Issues

  • Unable to add catalogs from VMware Cloud Director Object Storage Extension to VMware Cloud Director libraries for Cloud Director 10.3 and later

    When tenant users create a new catalog and click "Add to libraries" to upload an object, the import of the object fails.

  • The object lock feature does not work for Cloudian 7.4 or later

    You cannot use the object lock feature if you use Cloudian 7.4 or later.

  • Some tenant users cannot create buckets

    When using the ECS platform, some tenant users cannot create buckets if their corresponding IAM user in ECS has been removed manually by the ECS administrator.

  • Tenant users that log in with OpenID Connect cannot make S3 API calls

    When tenant users log in to VMware Cloud Director with OpenID Connect and they have been assigned a "Defer to Identity Provider" global role in VMware Cloud Director, they cannot access the S3 API by using the Access Key and Secret Key from the Security Credentials.

  • Tenant administrators cannot edit subordinate roles when they log in with OpenID Connect

    When tenant administrators log in to VMware Cloud Director with OpenID Connect and they have been assigned a "Defer to Identity Provider" global role in VMware Cloud Director, they cannot edit subordinate roles for other tenant users.

  • The Access Key and Secret Key pair is not displayed immediately after a tenant user logs in to VMware Cloud Director portal when using the DELL ECS platform

    When a tenant user onboards to VMware Object Storage Extension for the first time, the access key and secret key pair is not displayed immediately in the Security Credentials tab. 

  • You cannot back up and restore Kubernetes clusters if you use Dell ECS

    If the backend is configured with DELL ECS, the Kubernetes cluster protection button in the tenant portal is inactive.

  • The Permissions and Lifecycle tabs in the tenant portal are not displayed

    Tenant users that are mapped to IAM of ECS 3.6 or later cannot view the Permissions and Lifecycle tabs in the VMware Cloud Director Object Storage Extensions tenant portal.

  • Kubernetes clusters are not listed in VMware Cloud Director Object Storage Extension for Container Service Extension (CSE) 3.2 and later

    When a tenant administrator tries to back up a Kubernetes cluster for CSE 3.2 or later, the tenant cannot see the Kubernetes clusters list in VMware Cloud Director Object Storage Extension.

Caveats and Limitations

  • 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.

  • 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.

  • 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.

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.

  • 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.

  • 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 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.

  • You cannot unprotect a Kubernetes cluster which is disconnected from Object Storage Extension

    When a tenant administrator tries to unprotect a protected Kubernetes cluster, which is disconnected from Object Storage Extension, the operation fails.

    Workaround 1: Re-connect the Kubernetes cluster to Object Storage Extension.

    Workaround 2: Delete the relevant records in the Object Storage Extension database tables external_cluster_info and cluster_protection_info.

  • Object count metrics on the bucket do not reflect the correct value

    When a tenant user uploads multiple objects to a bucket, the object count on the bucket properties displays a lower number than the actual number of objects.

    Workaround: Click the SYNC button on the bucket.

  • The third party adapter for Object Storage Interoperability Service (OSIS) cannot run successfully

    If the third party object storage adapter for OSIS does not implement the API /api/v1/console, the OSIS adapter cannot run successfully.

    Workaround: Implement /api/v1/console with a blank link.

  • Object versioning does not work for the third party object storage integration with VMware Cloud Director by Object Storage Interoperability Service (OSIS)

    If the third party object storage system designs object version ID longer than 40 chars, the mapping to Object Storage Extension fails and object versioning cannot work.

    Workaround: None.

  • Third-party object storage platforms cannot be integrated with OSIS when S3 is configured with HTTPS

    When using a third-party object storage platform, which is integrated with OSIS (Object Storage Interoperability Service), the bucket creation fails due to the backend trust anchors error for SSL certificates.

    Workaround: Configure third-party object storage S3 with HTTP or request a hotfix from VMware.

  • For DELL ECS platform, creating two buckets with the same name across two different tenants results in an overwriting of the existing bucket in the first tenant

    When you create a bucket with the same name accross different tenants, the initial bucket is replicated along with the content of the bucket. This content can then managed by all of these users.

    Workaround: Request a hotfix upon 2.1.1.1 from VMware.

  • 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.

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