You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Krishna Kumar Asawa (Jira)" <ji...@apache.org> on 2023/08/02 06:42:00 UTC
[jira] [Commented] (HDDS-6536) INTERNAL_ERROR with ozonesecure docker-compose
[ https://issues.apache.org/jira/browse/HDDS-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750130#comment-17750130 ]
Krishna Kumar Asawa commented on HDDS-6536:
-------------------------------------------
Can we check if this is still a issue ?
> INTERNAL_ERROR with ozonesecure docker-compose
> ----------------------------------------------
>
> Key: HDDS-6536
> URL: https://issues.apache.org/jira/browse/HDDS-6536
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone CLI
> Reporter: Soumitra Sulav
> Assignee: Muskan Mishra
> Priority: Major
>
> While trying to deploy ozone cluster via docker-compose from {{hadoop-ozone/dist/target/compose/ozonesecure}} seeing below error on accessing tenant API.
> {code:java}
> sh-4.2$ ozone tenant create trial
> 2022-03-25 12:13:08,038 [main] INFO rpc.RpcClient: Creating Tenant: 'trial', with new volume: 'trial'
> INTERNAL_ERROR No subject alternative DNS name matching ranger found. {code}
> Components deployed as part of docker-compose
> {code:java}
> MacBook-Pro-2:ozonesecure ssulav$ docker-compose up -d
> Creating network "ozonesecure_default" with the default driver
> Creating ozonesecure_datanode_1 ... done
> Creating ozonesecure_recon_1 ... done
> Creating ozonesecure_kdc_1 ... done
> Creating ozonesecure_s3g_1 ... done
> Creating ozonesecure_ranger_1 ... done
> Creating ozonesecure_kms_1 ... done
> Creating ozonesecure_scm_1 ... done
> Creating ozonesecure_om_1 ... done {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org