You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2017/12/11 20:20:00 UTC
[jira] [Updated] (AMBARI-22629) Disabling Kerberos after enabled
during Blueprint install fails with missing data directory error
[ https://issues.apache.org/jira/browse/AMBARI-22629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Levas updated AMBARI-22629:
----------------------------------
Attachment: screenshot-error-dialog.png
> Disabling Kerberos after enabled during Blueprint install fails with missing data directory error
> -------------------------------------------------------------------------------------------------
>
> Key: AMBARI-22629
> URL: https://issues.apache.org/jira/browse/AMBARI-22629
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: blueprints, kerberos
> Attachments: screenshot-error-dialog.png
>
>
> Disabling Kerberos after enabled during Blueprint install fails with missing data directory error.
> !image-2017-12-11-15-12-21-492.png|thumbnail!
> This is caused by an invalid security state set for the installed components since the appropriate state is not set while enabling Kerberos during the installation process:
> {noformat}
> ambari=> select * from hostcomponentstate;
> id | cluster_id | component_name | version | current_state | host_id | service_name | upgrade_state | security_state
> ----+------------+------------------+--------------+---------------+---------+--------------+---------------+----------------
> 1 | 2 | KERBEROS_CLIENT | UNKNOWN | INSTALLED | 1 | KERBEROS | NONE | UNSECURED
> 2 | 2 | ZOOKEEPER_CLIENT | 2.5.0.0-1245 | INSTALLED | 1 | ZOOKEEPER | NONE | UNSECURED
> 3 | 2 | ZOOKEEPER_SERVER | 2.5.0.0-1245 | STARTED | 1 | ZOOKEEPER | NONE | UNSECURED
> {noformat}
> The expected state for each component is {{SECURED}}, not {{UNSECURED}}. Because of this, Ambari _thinks_ there is no work to be done, causing this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)