This is a tracking bug for Change: More flexible use of SSSD fast cache for local users For more details, see: https://fedoraproject.org/wiki/Changes/FlexibleLocalUserCache Allow to switch SSSD’s fast cache for local users on and off at runtime and do not start it by default anymore. If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
On Tuesday, 24 August we reached the Change Checkpoint: Completion deadline (100% complete). At this milestone all the F35 Changes should be fully complete, which is indicated by "ON_QA" status of a tracking bug. If you wish to defer this Change to F36, please needinfo bcotton
Hi, sorry, I forgot to change the status. From the 3 item mentioned on the change page the change to - the SSSD package was done in https://src.fedoraproject.org/rpms/sssd/c/bfbe7140ec88e5bfdcb56854c71d0300850b8253?branch=f35 - the authselect package was done by the rebase to the latest release in https://src.fedoraproject.org/rpms/authselect/c/5b2aadc5ec6bcd9adca994afcb60328123a936d8?branch=f35 - the glibc package https://src.fedoraproject.org/rpms/glibc/pull-request/33 was rejected by the glibc maintainers because they prefer that the ownership of the nsswitch.conf file will be moved to authselect which is planned for Fedora 36 Imo the missing change to nsswitch.conf is not a blocker because even if SSSD is not running calling the libnss_sss module to check if SSSD is running will only cause a minimal delay in the user and group lookups. On systems where authselect is called the order will be corrected by authselect. Please let me know if this is something which requires further discussion? For the time being I'll switch the ticket to ON_QA. bye, Sumit
F35 was released today. Closing the trackers.