Bug 2149344
Summary: | Failures have been seen during non-CA replica installation, frequently when certmonger is trying to retrieve certificates, getting CA_REJECTED | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | cilmar <cilmar> |
Component: | ipa | Assignee: | Rob Crittenden <rcritten> |
Status: | CLOSED MIGRATED | QA Contact: | ipa-qe <ipa-qe> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.6 | CC: | frenaud, rcritten, tscherf |
Target Milestone: | rc | Keywords: | MigratedToJIRA, Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-18 23:16: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
cilmar@redhat.com
2022-11-29 16:27:50 UTC
We believe this is related to racing replication. We will pick one server to be used throughout a server installation to prevent this. Fixed upstream master: https://pagure.io/freeipa/c/45fa43540f6a436c94f0484cec6e252e99d06fa7 Additional patch on master: https://pagure.io/freeipa/c/f248b22ef4d98293224b49576f5e6a1b8d672d76 Fixed upstream ipa-4-9: https://pagure.io/freeipa/c/3af7747364d184c8ef5bad8ea1654b12c529727b https://pagure.io/freeipa/c/0cf6292f9c5d0cb31d57439e234a4e8640edc64f Fixed upstream ipa-4-11: https://pagure.io/freeipa/c/54a251bceaabfaf82d0a18b2614c261e2bded0c0 https://pagure.io/freeipa/c/169f9abb6b9fdc11dc5d3e4ec8e6e9c3ef4dfd4f Fixed upstream ipa-4-10: https://pagure.io/freeipa/c/08dad8f8d75b965eb7c113a5710b0b3519df41dc https://pagure.io/freeipa/c/74f664685a4e689f0fd42e253310425b97d6c4ea Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |