[SERVER-46837] Add tracing around keytab check in mongokerberos test Created: 12/Mar/20  Updated: 20/Mar/20  Resolved: 20/Mar/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Trivial - P5
Reporter: Adam Cooper (Inactive) Assignee: Adam Cooper (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-46970 KRB5_CCNAME variable is reused betwee... Closed
Sprint: Security 2020-03-23
Participants:
Linked BF Score: 16

 Description   

An unknown failure in resolving the keytab cause test failure twice (BF-16430), but I have been unable to reproduce the failure after running the test many thousands of times. The best course of action might just be to add some additional tracing around the keytab check, such as printing out the contents of the keytab and credentials cache before performing the assert. This way, we can have some more information if it happens again.



 Comments   
Comment by Adam Cooper (Inactive) [ 20/Mar/20 ]

The actual bug that caused the related issue was discovered and fixed, so this ticket is unnecessary..

Generated at Thu Feb 08 05:12:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.