Created attachment 1829635 [details] ipa-healthcheck log files Description of problem: After upgrading from Fedora 34 to Fedora 35, the LDAP backend for FreeIPA becomes unresponsive after an indeterminate time period. This results in many problems, such as DNS queries returning an empty response for zones hosted in FreeIPA. FreeIPA tools, such as ipactl, and ipa-healthcheck also hang while they wait for a response from the LDAP server. Version-Release number of selected component (if applicable): 4.9.7-1.fc35 How reproducible: 100% Steps to Reproduce: 1. Install Fedora 34 2. Install freeipa-server & freeipa-server-dns 3. DNF system upgrade to Fedora 35 4. Wait until FreeIPA become unresponsive. Usually noticed as internal DNS issues Actual results: ex. DNS issue: [david@ipa-01 ~]$ dig @10.0.0.2 ipa-01.evilduckie.lan. a ; <<>> DiG 9.16.21-RH <<>> @10.0.0.2 ipa-01.evilduckie.lan. a ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached Expected results: [david@ipa-01 ~]$ dig @ipa-01 ipa-01.evilduckie.lan a ; <<>> DiG 9.16.21-RH <<>> @ipa-01 ipa-01.evilduckie.lan a ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51983 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; COOKIE: 0b76330806706d5a010000006152057eab84731e657ff490 (good) ;; QUESTION SECTION: ;ipa-01.evilduckie.lan. IN A ;; ANSWER SECTION: ipa-01.evilduckie.lan. 1200 IN A 10.0.0.2 ;; Query time: 0 msec ;; SERVER: 10.0.0.2#53(10.0.0.2) ;; WHEN: Mon Sep 27 11:55:10 CST 2021 ;; MSG SIZE rcvd: 94
Created attachment 1829636 [details] Stack trace files from IPA-01
Created attachment 1829637 [details] Stack trace files from IPA-02
I have used ipa-compat-manage and configured both IPA-01 and IPA-02 as 'disabled'.
Are you still seeing the issue after disabling the compat tree?
I started seeing symptoms of DNS errors this morning. There is a small Prometheus installation running which lost the ability to resolve all of the nodes on the local network via hostname. I have since checked both ipa-01 and ipa-02 and things seem to be okay: [david@ipa-01 ~]$ dig @ipa-01 ipa-wlan-01.evilduckie.lan a +short 10.0.0.4 [david@ipa-01 ~]$ dig @ipa-02 ipa-wlan-01.evilduckie.lan a +short 10.0.0.4 I restarted (HUP'ed) Prometheus and things seem to be better. uptime on ipa-01 and ipa-02 is about 3 days, so I'll watch them for the next couple of days and let you know if any issues pop up.
Everything seems to be running properly since disabling the compat tree.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.