[
https://issues.apache.org/jira/browse/HDDS-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811362#comment-16811362
]
Bharat Viswanadham commented on HDDS-1399:
------------------------------------------
Hi [~hgadre]
ThankYou for reporting this issue. Could you try the list Volume as suggested,
and let us know if it is working for you or not.
When S3Bucket is created, the volume is created with the user name as
"awsAccessKeyID".
When you list volumes, it will return volumes of the user running this command.
So, this volume will not be shown during list Volumes.
So, to get volume created by s3Bucket pass userName for list Volume.
ozone sh volume list --user=<<awsAccessKeyID>>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
