rajujith opened a new issue, #8665:
URL: https://github.com/apache/cloudstack/issues/8665
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Cloudstack Object storage
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Cloudstack object storage was added to 4.19, using the MinIO.
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
MinIO
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Although CSOS allows the creation of buckets with versioning enabled it
can't operate on the versions. Since the versions are not accessible through
the object storage UI we can't delete a bucket with versioning enabled if there
are older versions of the objects still present. This is could be handled by
using MinIO directly but it would be good to have it done using cloudstack
itself.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Create a MinIO server
2. Add the minIO server to cloudstack as object storage
3. Add a bucket with versioning enabled
4. Upload an object
5. Upload a new version of the object
6. verify that the older version is not listed
7. Delete all the objects and delete the bucket
~~~
<!-- You can also paste gist.github.com links for larger files -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
