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: Inspect the database code for proper transaction usage #4833

Closed
sssd-bot opened this issue May 2, 2020 · 1 comment
Closed

KCM: Inspect the database code for proper transaction usage #4833

sssd-bot opened this issue May 2, 2020 · 1 comment

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3839

  • Created at 2018-09-26 15:19:37 by jhrozek
  • Assigned to nobody

Some KCM operations run multiple operations on the secrets database. We should inspect the code to see if transactions are used properly.

Comments


Comment from jhrozek at 2018-10-03 14:36:21

Metadata Update from @jhrozek:

  • Issue priority set to: major (was: minor)
  • Issue set to the milestone: SSSD 2.1

Comment from jhrozek at 2019-02-22 15:21:57

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

Comment from jhrozek at 2019-06-13 23:10:45

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

Comment from thalman at 2020-03-11 11:57:12

Metadata Update from @thalman:

  • Issue tagged with: Next milestone
@pbrezina
Copy link
Member

pbrezina commented Jul 7, 2020

Everything seems to be fine to me. There are no transactions in KCM but all operations do just one thing there so there is nothing to rollback in case of failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants