Please describe the full procedure you used to retest.
> On May 29, 2015, at 9:28 AM, Yohan Bismuth <[email protected]> wrote:
>
> ...but i got the same problem using this method instead
>
> On Fri, May 29, 2015 at 3:25 PM, Yohan Bismuth <[email protected]>
> wrote:
>
>> oops my bad, was not looking the good thing
>>
>> On Fri, May 29, 2015 at 3:13 PM, Jon Maron <[email protected]> wrote:
>>
>>> It’s declared as public static:
>>>
>>> public synchronized static boolean isLoginKeytabBased()
>>>
>>> at least the version I’m looking at
>>>
>>>> On May 29, 2015, at 8:52 AM, Yohan Bismuth <[email protected]>
>>> wrote:
>>>>
>>>> Mmh I can't compile this. I don't think you can use isLoginKeytabBased()
>>>> since isKeytab is private in ugi.
>>>>
>>>> On Fri, May 29, 2015 at 1:56 PM, Jon Maron <[email protected]>
>>> wrote:
>>>>
>>>>> Looks like you’ve found a bug: validateLoginUser should be calling
>>>>> isLoginKeytabBased(), not isFromKeytab(). Would mind filing a JIRA?
>>>>>
>>>>> — Jon
>>>>>
>>>>>> On May 29, 2015, at 5:24 AM, Yohan Bismuth <[email protected]>
>>>>> wrote:
>>>>>>
>>>>>> Btw, i've tried using java7 and java8: smae issue.
>>>>>> I'm correctly logged as the principal of my keytab, and i can submit
>>> jobs
>>>>>> (like a wordcount) using this keytab.
>>>>>>
>>>>>> If i remove this line from the code:
>>>>>>
>>>>>>> validateLoginUser(UserGroupInformation.getLoginUser());
>>>>>>
>>>>>> everything seems to work fine.
>>>>>>
>>>>>> hasKerberosCredentials returns true, so the login must be based on a
>>>>>>> kerberos ticket. Perhaps it has expired?
>>>>>>
>>>>>> Well, this is the point here, i don't want the login to be based on a
>>>>>> kerberos ticket (because it would mean the ugi has the wrong flag set
>>> to
>>>>>> true). I want the login to be based on a kerberos key.
>>>>>>
>>>>>>
>>>>>> 2015-05-29 8:49 GMT+02:00 Jean-Baptiste Note <[email protected]>:
>>>>>>
>>>>>>> C'est pas très grave pour nous c'est packagé à la cradoc pour
>>> l'instant.
>>>>>>> C'est peut-etre aussi le fix ! Faudrait faire un git blame pour
>>>>> comprendre
>>>>>>> pourquoi l'exception est là. Elle trigge peut-etre aussi dans un cas
>>>>>>> légitime ?
>>>>>>>
>>>>>>> Question subsidiaire: tu soumets bien le job en tant que
>>>>>>> [email protected] et pas [email protected] ? (c'est
>>> la
>>>>>>> meme question que: tu as fait kinit en plus subtil)
>>>>>>> Tu as essayé avec un krb5.conf qui mette bien HPC.CRITEO.PREPROD en
>>>>>>> default realm sur la gateway.
>>>>>>>
>>>>>>> JB
>>>>>>>
>>>>>>> 2015-05-28 23:05 GMT+02:00 Yohan Bismuth <[email protected]>:
>>>>>>>
>>>>>>>> Bah ça implique de modifier et recompiler slider. Je sais pas si on
>>>>> veut
>>>>>>>> ça...
>>>>>>>>
>>>>>>>> 2015-05-28 22:20 GMT+02:00 Jean-Baptiste Note <[email protected]>:
>>>>>>>>
>>>>>>>>> OK j'ai rien dit :)
>>>>>>>>> Tu peux spécifier tout ça dans le thread, si vraiment ça fonctionne
>>>>> sans
>>>>>>>>> l'exception, je vois même pas pourquoi on s'embête en fait ???
>>>>>>>>>
>>>>>>>>> JB
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jean-Baptiste Note
>>>>>>>
>>>>>
>>>>>
>>>
>>>
>>
