[ https://issues.apache.org/jira/browse/KUDU-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated KUDU-1976: ------------------------------ Target Version/s: 1.5.0 Code Review: https://gerrit.cloudera.org/#/c/7850/ > MiniKdc races between add_principal and kinit > --------------------------------------------- > > Key: KUDU-1976 > URL: https://issues.apache.org/jira/browse/KUDU-1976 > Project: Kudu > Issue Type: Bug > Components: java, test > Affects Versions: 1.4.0 > Reporter: Adar Dembo > Assignee: Todd Lipcon > > 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. > {noformat} > 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 testu...@krbtest.com; defaulting to no policy > 02:36:16.269 [DEBUG - main] (MiniKdc.java:363) Authenticating as principal > jenkins-slave/ad...@krbtest.com with password. > 02:36:16.269 [DEBUG - main] (MiniKdc.java:363) Principal > "testu...@krbtest.com" 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 > 'testu...@krbtest.com' not found in Kerberos database while getting initial > credentials > {noformat} > 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). -- This message was sent by Atlassian JIRA (v6.4.14#64029)