[
https://issues.apache.org/jira/browse/HDDS-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal resolved HDDS-1399.
---------------------------------
Target Version/s: (was: 0.7.0)
Resolution: Not A Problem
S3 Gateway no longer uses generated volume names.
> Ozone cli does not list system generated volumes
> ------------------------------------------------
>
> Key: HDDS-1399
> URL: https://issues.apache.org/jira/browse/HDDS-1399
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Affects Versions: 0.4.0
> Environment: Docker based Ozone cluster with latest code from trunk.
> Reporter: Hrishikesh Gadre
> Priority: Minor
>
> The docker setup for Ozone S3 gateway creates a volume in Ozone for storing
> the buckets created via S3 API. I found that the "ozone sh volume list"
> command does not include this volume information in its result. But the
> volume identifier can be found by using "ozone s3 path <bucket_name>" command
> and the volume information can be found by using "ozone sh volume info
> <volume_id>". Since the CLI results are not consistent across various
> commands, it can be confusing for the users. This Jira is to ensure that
> "ozone sh volume list" command returns information for both (a) user
> generated and (b) system generated volumes.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
