You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/10/23 19:43:00 UTC
[jira] [Updated] (HDDS-2352) Client gets internal error instead of
volume not found in secure cluster
[ https://issues.apache.org/jira/browse/HDDS-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-2352:
---------------------------------
Labels: pull-request-available (was: )
> Client gets internal error instead of volume not found in secure cluster
> ------------------------------------------------------------------------
>
> Key: HDDS-2352
> URL: https://issues.apache.org/jira/browse/HDDS-2352
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
> Reporter: Attila Doroszlai
> Assignee: Attila Doroszlai
> Priority: Minor
> Labels: pull-request-available
>
> New Freon generators create volume and bucket if necessary. This does not work in secure cluster for volume, but works for bucket:
> {code}
> $ cd hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/compose/ozonesecure
> $ docker-compose exec scm bash
> $ kinit -kt /etc/security/keytabs/testuser.keytab testuser/scm@EXAMPLE.COM
> $ ozone freon ockg -n 1
> ...
> Check access operation failed for volume:vol1
> ...
> Successful executions: 0
> $ ozone sh volume create vol1
> $ ozone freon ockg -n 1
> ...
> 2019-10-23 18:30:27,279 [main] INFO - Creating Bucket: vol1/bucket1, with Versioning false and Storage Type set to DISK and Encryption set to false
> ...
> Successful executions: 1
> {code}
> The problem is that {{VOLUME_NOT_FOUND}} result is lost during ACL check, and client gets {{INTERNAL_ERROR}} instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org