[KUDU-1976] MiniKdc races between add_principal and kinit

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.6.0
• Component/s: java, test
• Target Version/s: 1.5.0
• Code Review: https://gerrit.cloudera.org/#/c/7850/
• Assignee: Todd Lipcon
• Reporter: Adar Dembo
• Created: 19/Apr/17 19:24
• Updated: 01/Sep/17 20:21
• Resolved: 01/Sep/17 20:21

Description

Noticed this in a recent precommit run, in ASAN mode, but I recall seeing it before too. I think it happens from time to time.

02:36:16.240 [DEBUG - main] (MiniKdc.java:339) executing '/usr/sbin/kadmin.local -q add_principal -pw testuser testuser', env: '...'
02:36:16.268 [DEBUG - main] (MiniKdc.java:363) WARNING: no policy specified for [e-mail]; defaulting to no policy
02:36:16.269 [DEBUG - main] (MiniKdc.java:363) Authenticating as principal jenkins-slave/[e-mail] with password.
02:36:16.269 [DEBUG - main] (MiniKdc.java:363) Principal "[e-mail]" created.
02:36:16.274 [DEBUG - main] (MiniKdc.java:339) executing '/usr/bin/kinit testuser', env: '...'
02:36:16.277 [DEBUG - main] (MiniKdc.java:363) kinit: Client '[e-mail]' not found in Kerberos database while getting initial credentials

I wonder why the kinit doesn't take immediately. I went looking for a "sync" option for the KDC but couldn't find one; perhaps it's a bug in the version of the KDC used in the test environment? (Ubuntu 14.04 IIRC).

If there's no such thing, maybe we should retry kinit with some backoff until it works (or fails for good).