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.
Fixed the patch.
Was actually asking if this change would make it into the regular (non-Z) stream.
Comment 9Nikolai Kondrashov
2016-09-30 11:35:40 UTC
Thanks a lot on the patch update and following the developers on this, Mike.
I cannot promise an asynchronous update, unfortunately. You will have to reach support on this as a customer, explicitly.
Please hold work on this. The proposed fix does not work:
#0 0x00007f48dfea1416 in check_for_realm (instance=<optimized out>, request=0x7f48e7870830,
returnrealm=0x7f48dc18d580) at src/modules/rlm_realm/rlm_realm.c:276
276 if (realm->acct_pool->servers[i]->ipaddr.af == AF_UNSPEC) continue;
(gdb) bt
#0 0x00007f48dfea1416 in check_for_realm (instance=<optimized out>, request=0x7f48e7870830,
returnrealm=0x7f48dc18d580) at src/modules/rlm_realm/rlm_realm.c:276
Comment 19Nikolai Kondrashov
2017-02-15 15:55:54 UTC
Hi Mike, do you have any update on this issue? Have you discovered the source, a fix?
None at this time. I'd love it if Alan DeKok or one of his leads would participate here as the issue is pretty deep within Freeradius and they'd be best positioned to help.
Comment 21Nikolai Kondrashov
2017-02-16 07:27:13 UTC
I see. Before we can fix this, we'll need a way to reproduce this, preferably automatic one, or at least exact instructions. Also, please reach support on this one, if you're a customer.
Comment 22Nikolai Kondrashov
2017-02-22 13:17:11 UTC
Mike, please note that if we don't get a way to reproduce this, we won't be able to investigate it, and thus get a fix for this into next RHEL release.
Comment 23Nikolai Kondrashov
2017-03-27 12:50:06 UTC
Closing as WORKSFORME as we have no reproducer. Please feel free to reopen, once you have one.