[
https://issues.apache.org/jira/browse/HDDS-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837439#comment-17837439
]
Siyao Meng commented on HDDS-10694:
-----------------------------------
But yeah in this specific case the error message could be better parsed to just
say "user doesn't exist". But ozone client does not have such logic right now.
So it returns error as-is.
> Tenant API throwing internal error exception on the console
> -----------------------------------------------------------
>
> Key: HDDS-10694
> URL: https://issues.apache.org/jira/browse/HDDS-10694
> Project: Apache Ozone
> Issue Type: Bug
> Components: s3gateway
> Affects Versions: 1.5.0
> Reporter: Soumitra Sulav
> Priority: Major
> Labels: ozone-upstream
>
> On an invalid user, the tenant API is dumping internal exception message on
> the client console
> {code:java}
> [[email protected] ~]# ozone tenant user assign
> scm/ccycloud-1.quasar-vqbgau.root.comops.site --tenant=test
> 24/04/15 11:46:57 INFO protocolPB.OmTransportFactory: Loading OM transport
> implementation
> org.apache.hadoop.ozone.om.protocolPB.Hadoop3OmTransportFactory as specified
> by configuration.
> 24/04/15 11:46:58 INFO client.ClientTrustManager: Loading certificates for
> client.
> TENANT_AUTHORIZER_ERROR java.io.IOException:
> org.apache.ranger.RangerServiceException: Ranger API
> org.apache.ranger.RangerClient$API@18f17eea failed: statusCode=400,
> status=Bad Request, response:{"statusCode":1,"msgDesc":"user with name:
> scm/ccycloud-1.quasar-vqbgau.root.comops.site does not exist
> ","messageList":[{"name":"INVALID_INPUT_DATA","rbKey":"xa.validation.invalid_input_data","message":"Invalid
> input data"}]} {code}
> There is no need for user to experience such messages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
