[AMBARI-25173] Regenerate keytab skips some keytabs on repaired host

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Cannot Reproduce
• Affects Version/s: 2.7.3
• Fix Version/s: 2.7.4
• Component/s: ambari-server
• Labels: pull-request-available
• Assignee: Dmitry Lysnichenko
• Reporter: Dmitry Lysnichenko
• Created: 27/Feb/19 18:08
• Updated: 01/Mar/19 21:36
• Resolved: 01/Mar/19 21:35

Description

STR

After repairing a failed master node (single, not HA). Ambari has external db. Repair should also work if cluster is kerberized. Repair means following procedure (some steps are skipped for clarity):

1. terminate failed node, start a new one
2. start ambari on new node
3. regenerate all keytabs
4. reinstall components
5. start / restart all components

Ambari has external db, containing the successful installation before repair.

The problem

When calling regenerate keytabs some do get created without any keys:

• smokeuser.headless.keytab
• spnego.service.keytab

Quick analysis revealed that in case of some of the keytabs ambari stores to db a cache location on the hard drive. Since, however, that cache is note there on the new instance and so ambari for some reason fails to regenerate those specific keytabs.

Version where this worked
In ambari version 2.7.1.0 this has already worked.

Issue Links

• links to: GitHub Pull Request #2839