Bug 1906802
Summary: | sssd-2.4.0-3.fc33 breaks kinit | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Karel Volný <kvolny> |
Component: | sssd | Assignee: | Pavel Březina <pbrezina> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 33 | CC: | abokovoy, atikhono, jhrozek, lslebodn, mzidek, pbrezina, rharwood, sbose, ssorce, sssd-maintainers |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | sssd-2.4.0-4.fc33 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-12-16 01:42:47 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: |
Description
Karel Volný
2020-12-11 12:52:18 UTC
I guess this should be fixed in https://github.com/SSSD/sssd/pull/5432 Yes, Though I unpushed the update immediately, so it has definitely not been pushed to stable and should not even be available in updates-testing. Unfortunately, koji is unresponsive today so I'm not able to create a new update. FEDORA-2020-b61158b5ff has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b61158b5ff FEDORA-2020-b61158b5ff has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b61158b5ff` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b61158b5ff See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-b61158b5ff has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |