Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Discovering and contacting all DC addresses for a large domain is a potentially nearly unbounded operation. We have to stop somewhere, so we chose to contact 3 addresses.
Please reopen if this is an actual problem. Do you have a use case this breaks?Otherwise this is NOTABUG.
Well, there isn't a real use case I'm just trying to test a scenario where the IPv6 network is down between the host and server. And wen there are 3 IPv6 addresses realm newer tries IPv4, the only one that actually works.
I can fix it by removing one IPv6 address, so not a big deal. I just wanted to see if this is by purpose.
I did some research how exactly it works and it looks like this:
realmd tries to connect to remote ldap with the first 3 addresses and where no response is returned withing 15 sec. it quits with no result.
If and error (e.g. icmp net unreachable) is returned from one of the addresses the next address from the pool is picked and that is tried and so on. All this within the first 15 seconds.
This mechanisms seems to be ok, when errors are returned, but IMHO it could be more robust when no error is returned. For example try more (all) addresses (maybe not at once but e.g. 3 every 1 second) until one is answered. And timeout after 15 secs as it is. But this is really a marginal case, so feel free to close it as not a bug (and definitely we shouldn't bother with it in RHEL-7.0).
This does not have a solid real world use case. I'm not against someone providing and including a patch for this, but I'm unable to spend time fixing what seems like an extreme edge case.
Comment 9RHEL Program Management
2015-07-14 18:37:54 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.