[HDDS-2352] Client gets internal error instead of volume not found in secure cluster

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Component/s: Ozone Manager
• Labels: pull-request-available
• Target Version/s: 0.5.0
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 23/Oct/19 18:38
• Updated: 24/Feb/20 20:49
• Resolved: 24/Oct/19 00:20

Description

New Freon generators create volume and bucket if necessary. This does not work in secure cluster for volume, but works for bucket:

$ 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/[e-mail]
$ 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

The problem is that VOLUME_NOT_FOUND result is lost during ACL check, and client gets INTERNAL_ERROR instead.

Issue Links

• links to: GitHub Pull Request #76