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

New or modified ID-View User overrides are not visible unless rm -f /var/lib/sss/db/*cache* #4125

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Assignees
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

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


Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1354414

Description of problem:
When adding a new Override or modifying an existing one in IPAs ID-View, the
changes are not visible to the systems in question.

Version-Release number of selected component (if applicable):
sssd-1.13.0-40.el7_2.9

How reproducible:
Always

Steps to Reproduce:
1.id tester
uid=1001(tester) gid=1002 groups=1002,94800003(satorgadmin),94800008(oradba)
2. Change User override in IPA
3. sss_cache -E && systemctl restart sssd
4. id tester
uid=1001(tester) gid=1002 groups=1002,94800003(satorgadmin),94800008(oradba)


Actual results:
See Steps to Reproduce


Expected results:

ID-View Overrides changes should be visible ideally instantly or within a
defined timeframe


Additional info:

As a workaround one can remove the cache files:
# systemctl stop sssd
# rm -f /var/lib/sss/db/*cache*
# systemctl start sssd

Comments


Comment from sbose at 2016-07-11 13:00:56

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
owner: somebody => sbose
review: True => 0
selected: =>
status: new => assigned
testsupdated: => 0


Comment from sbose at 2016-07-11 15:16:30

Fields changed

patch: 0 => 1


Comment from jhrozek at 2016-07-12 14:46:19

I think we should push into the stable branch as well.


Comment from jhrozek at 2016-07-13 11:57:23

(leaving open for triage)


Comment from jhrozek at 2016-07-14 17:35:46

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13.5
resolution: => fixed
status: assigned => closed


Comment from sbose at 2017-02-24 15:04:19

Metadata Update from @sbose:

  • Issue assigned to sbose
  • Issue set to the milestone: SSSD 1.13.5
@sssd-bot sssd-bot added Bugzilla Closed: Fixed Issue was closed as fixed. labels May 2, 2020
@sssd-bot sssd-bot closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

2 participants