Error "Storage user XXX does not belong to user YYY" when enabling the K8s Cluster protection within OSE plugin
book
Article ID: 377788
calendar_today
Updated On:
Products
VMware Cloud Director
Issue/Introduction
- VMware OSE shows username of different tenant when bucket creation failed
- When a user enables the K8s Cluster protection within OSE plugin the creation of the bucket fails when a bucket with the same name already exists.
- The error message "
Storage user XXX does not belong to user YYY
" is thrown and showing the user of a different Tenant which owns the existing bucket
Environment
VMware OSE 3.0.0-23443325
Cause
This is a known issue in OSE as the same bucket name should not be allowed when starting to protect the k8s Cluster.
Resolution
This issue is fixed in OSE 3.1.0.3 version which will warn you that you cannot start protecting a k8 Cluster using the same bucket name.
See Release Notes
Further improvement of the warning message will be added in future release of OSE.
Feedback
thumb_up
Yes
thumb_down
No