You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Bharat Viswanadham (Jira)" <ji...@apache.org> on 2020/09/04 05:24:00 UTC

[jira] [Resolved] (HDDS-3077) Lost volume after changing access key

     [ https://issues.apache.org/jira/browse/HDDS-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bharat Viswanadham resolved HDDS-3077.
--------------------------------------
    Resolution: Invalid

Now, this is not an issue, as we have removed the logic of to figure out the volume from credentials, and using fixed volume "s3v".

This behavior is changed by HDDS-3385.

> Lost volume after changing access key
> -------------------------------------
>
>                 Key: HDDS-3077
>                 URL: https://issues.apache.org/jira/browse/HDDS-3077
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: S3
>            Reporter: Beata Sudi
>            Priority: Critical
>
> When using the S3 API, Ozone generates the volume depending on the user's access key.  When the access key is changed, it becomes no longer reachable by the user.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org