[AMBARI-24555] Nifi Registry install fails

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 2.7.3
• Component/s: ambari-web
• Labels: pull-request-available
• Assignee: Andriy Babiichuk
• Reporter: Andriy Babiichuk
• Created: 28/Aug/18 14:44
• Updated: 22/Oct/18 21:00
• Resolved: 31/Aug/18 10:33

Description

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.

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
 

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 '/'.

Issue Links

• links to: GitHub Pull Request #2187
• links to: GitHub Pull Request #2188