[
https://issues.apache.org/jira/browse/AMBARI-13831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000471#comment-15000471
]
Hudson commented on AMBARI-13831:
---------------------------------
ABORTED: Integrated in Ambari-branch-2.1 #838 (See
[https://builds.apache.org/job/Ambari-branch-2.1/838/])
AMBARI-13831. After enabling kerberos with option 'Manage Kerberos (akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=65793f66a892af9e3f7079748517cc7921ad0d8b])
* ambari-web/app/controllers/wizard/step8_controller.js
* ambari-web/app/controllers/main/admin/kerberos.js
* ambari-web/test/controllers/main/admin/kerberos_test.js
* ambari-web/test/controllers/wizard/step8_test.js
> After enabling kerberos with option 'Manage Kerberos principals and keytabs
> manually', adding new component buttons will not respond
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-13831
> URL: https://issues.apache.org/jira/browse/AMBARI-13831
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 2.1.3
>
> Attachments: AMBARI-13831.patch
>
>
> PROBLEM: If customer enable kerberos, with the option 'Manage Kerberos
> principals and keytabs manually', when adding a new host component Ambari
> will not respond. After troubleshooting, we found that Ambari is issuing this
> API call:
> {code}
> http://{ambari-server}:8080/api/v1/clusters/{cluster_name}/services/KERBEROS?fields=Services/attributes/kdc_validation_result,Services/attributes/kdc_validation_failure_details&_=1446149280683
> {code}
> This will return '404 service kerberos not found', which is expected as
> Kerberos service will not be installed if 'manually manage keytab' option is
> chosen. If we use API to add the KERBEROS services, this issue went away
> BUSINESS IMPACT: User is not able to add host components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
