This release of VMware Cloud Director Object Storage Extension provides various bug fixes.
|
VMware Cloud Director Object Storage Extension 2.1.1.2 | 29 SEP 2022 | Build 20497421 Check for additions and updates to these release notes. |
This release of VMware Cloud Director Object Storage Extension provides various bug fixes.
You can upgrade directly to VMware Cloud Director Object Storage Extension 2.1.1.2 from versions 2.1.1.1, 2.1.1, 2.1, and 2.0. See Upgrading VMware Cloud Director Object Storage Extension.
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.
All documentation is available on the VMware Cloud Director Object Storage Extension Documentation page.
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.
This issue is now resolved.
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.
This issue is now resolved.
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.
This issue is now resolved.
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.
This issue is now resolved.
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.
This issue is now resolved.
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.
This issue is now resolved.
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.
