Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1869009
Summary: | Running ipa-replica-install fails with Failed to start replication | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan Pazdziora <jpazdziora> |
Component: | freeipa | Assignee: | IPA Maintainers <ipa-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | abokovoy, fdc, ipa-maint, jcholast, jhrozek, jpazdziora, mhjacks, pvoborni, rcritten, ssorce, twoerner |
Target Milestone: | --- | Keywords: | Regression |
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-08-16 19:27:11 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
Jan Pazdziora
2020-08-15 09:08:40 UTC
This was first shown in FreeIPA container CI: https://travis-ci.org/github/freeipa/freeipa-container/builds/717852685 But the problem is present outside of containers as well. This is almost certainly a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1868482 https://bodhi.fedoraproject.org/updates/FEDORA-2020-d10a284af3 was pushed to stable recently but I don't know if it's hit the repos yet. Can you re-test with this updated package? Thanks for the pointer, Rob. I confirm that with krb5-libs-1.18.2-20.fc32, ipa-replica-install passes. *** This bug has been marked as a duplicate of bug 1868482 *** |