[
https://issues.apache.org/jira/browse/AMBARI-24555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598658#comment-16598658
]
Hudson commented on AMBARI-24555:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9905 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9905/])
AMBARI-24555 Nifi Registry install fails. (ababiichuk) (ababiichuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=14811e4ff0049382e8f9496e9f3742ca0e141873])
* (edit) ambari-web/app/mixins/wizard/addSecurityConfigs.js
* (edit) ambari-web/test/mixins/wizard/addSeccurityConfigs_test.js
> Nifi Registry install fails
> ---------------------------
>
> Key: AMBARI-24555
> URL: https://issues.apache.org/jira/browse/AMBARI-24555
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.7.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Facing issue installing Nifi Registry on HDP_HDF cluster. The create keytab
> step in Ambari is failing during installation. Below exception is seen in
> ambari logs.
>
> {code}
> 2018-08-21 13:11:03,401 ERROR [Server Action Executor Worker 1305]
> CreatePrincipalsServerAction:309 - Failed to create principal, - Failed to
> create new principal - no principal specified
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationException:
> Failed to create new principal - no principal specified
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:268)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:157)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:460)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:748)
> 2018-08-21 13:11:03,401 INFO [Server Action Executor Worker 1305]
> KerberosServerAction:481 - Processing identities completed.
> 2018-08-21 13:11:04,191 ERROR [ambari-action-scheduler] ActionScheduler:482 -
> Operation completely failed, aborting request id: 117
> {code}
> The Ambari UI should not display any properties from Kerberos identity blocks
> that indicate they are referencing another Kerberos identity. There are 2
> ways we know this:
> - The new/preferred way: the identity block has a non-empty/non-null
> "reference" attribute
> - The old (backwards compatible way): the identity block has a "name"
> attribute the starts with a '/'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
