Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KCM: Fall back to using the first ccache if the default does not exist #706

Closed
wants to merge 1 commit into from

Conversation

Projects
None yet
2 participants
@jhrozek
Copy link
Contributor

commented Dec 4, 2018

Resolves: https://pagure.io/SSSD/sssd/issue/3838

KCM stores the default ccache in a separate DB entry. If the DB entry
contains a UUID that cannot be found in the DB for whatever reason, we
should just use the first ccache as the default. (This is what we already
do if there is no default)

KCM: Fall back to using the first ccache if the default does not exist
Resolves:
https://pagure.io/SSSD/sssd/issue/3838

KCM stores the default ccache in a separate DB entry. If the DB entry
contains a UUID that cannot be found in the DB for whatever reason, we
should just use the first ccache as the default. (This is what we
already do if there is no default)
@pbrezina

This comment has been minimized.

Copy link
Member

commented Mar 27, 2019

Ack.

@pbrezina pbrezina self-assigned this Mar 27, 2019

@pbrezina pbrezina added the Accepted label Mar 27, 2019

@jhrozek

This comment has been minimized.

Copy link
Contributor Author

commented Mar 27, 2019

@jhrozek jhrozek closed this Mar 27, 2019

@jhrozek jhrozek added the Pushed label Mar 27, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.