| Summary: | RHEL6 sssd upgrade restorecon workaround for /var/lib/sss/mc context | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | sssd | Assignee: | Jakub Hrozek <jhrozek> |
| Status: | CLOSED ERRATA | QA Contact: | Kaushik Banerjee <kbanerje> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.4 | CC: | ccoursey, dpal, ekeck, grajaiya, jgalipea, jhrozek, jsvarova, lslebodn, mgregg, mkosek, pbrezina, pm-eus, spoore |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | sssd-1.9.2-82.11.el6_4 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, RPM did not reload its labels database in a single transaction. Consequently, when sssd was upgraded and pulled in a new selinux-policy in a single transaction, the new context added by the selinux-policy-targeted utility was not used for the files in the /var/lib/sss/mc/ directory. To fix this bug, sssd has been set to run restorecon in the %post scriptlet until RPM can properly handle it, and thus correct context is set.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-20 11:05:08 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 987456 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2013-10-23 20:09:02 UTC
The customer has confirmed that the packages fixes his current issue. From the case# 00969058: <snip> I can confirm that this package fixes the issue we're having. <snip> --cliff (In reply to Clifton Coursey from comment #6) > The customer has confirmed that the packages fixes his current issue. > > From the case# 00969058: > > <snip> > I can confirm that this package fixes the issue we're having. > <snip> > > --cliff Great, thanks for testing! Any word on comment #5? Do they need a 6.5.z or can we give them access to the 6.5 bits? (In reply to Jakub Hrozek from comment #7) > (In reply to Clifton Coursey from comment #6) > > The customer has confirmed that the packages fixes his current issue. > > > > From the case# 00969058: > > > > <snip> > > I can confirm that this package fixes the issue we're having. > > <snip> > > > > --cliff > > Great, thanks for testing! Any word on comment #5? Do they need a 6.5.z or > can we give them access to the 6.5 bits? ping; Any news? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1742.html |