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

Posted to issues@ozone.apache.org by "George Huang (Jira)" <ji...@apache.org> on 2022/03/30 03:08:00 UTC

[jira] [Updated] (HDDS-6530) Newly add Ozone datanode failed to start due to kdc and admin_server entry in krb5.conf was not updated

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

George Huang updated HDDS-6530:
-------------------------------
    Summary: Newly add Ozone datanode failed to start due to kdc and admin_server entry in krb5.conf was not updated  (was: Add datanode to Ozone failed to start due to kdc and admin_server entry in krb5.conf was not updated)

> Newly add Ozone datanode failed to start due to kdc and admin_server entry in krb5.conf was not updated
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-6530
>                 URL: https://issues.apache.org/jira/browse/HDDS-6530
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Datanode
>            Reporter: George Huang
>            Priority: Major
>
> Adding new datanode to Ozone on a secured cluster with kerberos and TLS. Datanode failed to start after assigning Ozone datanode role. In particular if entries of kdc and admin_server in krb5.conf contains old value point to some other random host. The old value was not updated to reflect the newly assigned Ozone DN role in the new cluster.
> The result was DN failed to start. The expectation is corresponding entries in krb5.conf on these nodes got updated when assigned DN role for Ozone.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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