[
https://issues.apache.org/jira/browse/AMBARI-25173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-25173:
----------------------------------------
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.
was:
*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.
We are currently using 2.7.100.0-266
I also tried 2.7.3.0 and the issue is present there as well.
> Regenerate keytab skips some keytabs on repaired host
> -----------------------------------------------------
>
> Key: AMBARI-25173
> URL: https://issues.apache.org/jira/browse/AMBARI-25173
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.3
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Priority: Blocker
> Fix For: 2.7.4
>
>
> *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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
