You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/07/21 10:22:00 UTC
[jira] [Commented] (AMBARI-24320) SET_KEYTABS is preformed twice
per host during Kerberos operations
[ https://issues.apache.org/jira/browse/AMBARI-24320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551608#comment-16551608 ]
Hudson commented on AMBARI-24320:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9648 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9648/])
AMBARI-24320. Using the proper command name when creating a (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=13f96c6287677b867f550af48d013250cdbe8a2d])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java
> SET_KEYTABS is preformed twice per host during Kerberos operations
> ------------------------------------------------------------------
>
> Key: AMBARI-24320
> URL: https://issues.apache.org/jira/browse/AMBARI-24320
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> *STR*
> * Enable Kerberos and check the DB after the 'Test Kerberos' step, or
> * Regenerate keytabs on a secure cluster with the option 'Only regenerate keytabs for missing hosts and components' enabled (this is important, otherwise the issue is not reproducible)
> *Result:*
> {noformat}
> SELECT hrc.task_id, hrc.request_id, hrc.host_id, hrc.stage_id, st.request_context, hrc.status, hrc.role, hrc.role_command, hrc.custom_command_name FROM host_role_command hrc, stage st WHERE hrc.stage_id = st.stage_id AND hrc.request_id = st.request_id AND hrc.custom_command_name = 'SET_KEYTAB' ORDER BY request_id, host_id, stage_id;{noformat}
> ||task_id||request_id||host_id||stage_id||request_context||status||role||role_command||custom_command_name||
> |63|17|1|1|Checking keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |68|17|1|4|Distribute Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |64|17|2|1|Checking keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |69|17|2|4|Distribute Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |65|17|3|1|Checking keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |70|17|3|4|Distribute Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |83|19|1|1|Checking keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |88|19|1|4|Distribute Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |84|19|2|1|Checking keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |89|19|2|4|Distribute Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |85|19|3|1|Checking keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> |90|19|3|4|Distribute Keytabs|COMPLETED|KERBEROS_CLIENT|CUSTOM_COMMAND|SET_KEYTAB|
> *Expected result:*
> only one SET_KEYTAB command should be recorded
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)