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.
Version-Release number of selected component:
sssd-common-1.14.0-0.1.alpha.el7
Additional info:
reporter: libreport-2.1.11.1
backtrace_rating: 4
cmdline: /usr/libexec/sssd/sssd_be --domain spice.brq.redhat.com --uid 0 --gid 0 --debug-to-files
crash_function: ipa_dyndns_update_send
executable: /usr/libexec/sssd/sssd_be
global_pid: 1960
kernel: 3.10.0-451.el7.x86_64
pkg_vendor: Red Hat, Inc.
reproducible: Not sure how to reproduce the problem
runlevel: N 5
type: CCpp
uid: 0
Truncated backtrace:
Thread no. 1 (10 frames)
#0 ipa_dyndns_update_send at src/providers/ipa/ipa_dyndns.c:175
#1 ipa_dyndns_update at src/providers/ipa/ipa_dyndns.c:122
#2 be_run_cb_step at src/providers/data_provider_callbacks.c:96
#3 tevent_common_loop_timer_delay at ../tevent_timed.c:341
#4 epoll_event_loop at ../tevent_epoll.c:659
#5 epoll_event_loop_once at ../tevent_epoll.c:926
#6 std_event_loop_once at ../tevent_standard.c:114
#7 _tevent_loop_once at ../tevent.c:533
#8 tevent_common_loop_wait at ../tevent.c:637
#9 std_event_loop_wait at ../tevent_standard.c:140
clarification: I know you said you don't know exactly how to reproduce, but knowing what was the system doing at that time and sending the sssd logs if there are any would help.
Steeve, this is a crash, but we have no idea how it happened. If we want to include this fix in 7.3, it would only be through sanity testing. What do you think?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2016-2476.html