Bug 1758661

Summary: sssd logins break if sssd-kcm is removed
Product: [Fedora] Fedora Reporter: Gwyn Ciesla <gwync>
Component: sssdAssignee: Sumit Bose <sbose>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: abokovoy, amessina, jhrozek, lslebodn, mzidek, pbrezina, rharwood, sbose, ssorce, thalman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 18:41:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Configs none

Description Gwyn Ciesla 2019-10-04 18:50:10 UTC
Additional info in:

https://bugzilla.redhat.com/show_bug.cgi?id=1757224

Comment 1 Lukas Slebodnik 2019-10-04 20:54:12 UTC
Could you provide deterministic reproducer plus log files?

https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html

We might get different results in local testing without reasonable reproducer and thus we would not be able fix the bug.

Comment 2 Gwyn Ciesla 2019-10-07 14:40:32 UTC
Created attachment 1623152 [details]
Configs

Contains krb5.conf and sssd.conf.

I have an existing sssd/krb5 setup, and even if I'm not configured to use the KCM cache, if I remove sssd-kcm, I can no longer log in.

Comment 3 Ben Cotton 2020-11-03 15:37:48 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2020-11-24 18:41:33 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.