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.
Bug 2047788 - [NMCI] dhcp-timeout_infinity test failure
Summary: [NMCI] dhcp-timeout_infinity test failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Vladimir Benes
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-28 14:37 UTC by Vladimir Benes
Modified: 2022-05-17 16:08 UTC (History)
6 users (show)

Fixed In Version: NetworkManager-1.36.0-0.8.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:48:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-110219 0 None None None 2022-01-28 14:40:36 UTC
Red Hat Product Errata RHBA-2022:3915 0 None None None 2022-05-17 15:48:36 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1077 0 None opened [th/l3cfg-acd-crash] fix assertion failure in l3cfg's ACD handling during "instance-reset" 2022-01-28 21:59:30 UTC

Description Vladimir Benes 2022-01-28 14:37:15 UTC
Description of problem:
https://tools.dqe.lab.eng.bos.redhat.com/vbenes/nm_ci_stats/stats.html#project:beaker-NetworkManager-main-veth-rhel9-upstream;search:dhcp-timeout_infinity_timeout

the latest report is here:
https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-main-veth-rhel9-upstream/884/artifact/artifacts/FAIL_report_NetworkManager-ci_Test0391_dhcp-timeout_infinity.html

there seems to be a crash in the after scenario:
                Found module NetworkManager with build-id: ddb90e25f1b4eb918788f948629b8d124e67b129
                Stack trace of thread 209998:
                #0  0x00007f23be5257fc __pthread_kill_implementation (libc.so.6 + 0x8f7fc)
                #1  0x00007f23be4d8676 __GI_raise (libc.so.6 + 0x42676)
                #2  0x00007f23be4c27d3 __GI_abort (libc.so.6 + 0x2c7d3)
                #3  0x00007f23be6e5d4c g_assertion_message (libglib-2.0.so.0 + 0x1ed4c)
                #4  0x00007f23be74698f g_assertion_message_expr (libglib-2.0.so.0 + 0x7f98f)
                #5  0x00005629ac937e46 _l3_acd_data_state_change (NetworkManager + 0x1fce46)
                #6  0x00005629ac939f4d _l3_acd_data_timeout_cb (NetworkManager + 0x1fef4d)
                #7  0x00007f23be71c5a1 g_timeout_dispatch (libglib-2.0.so.0 + 0x555a1)
                #8  0x00007f23be71bd4f g_main_context_dispatch (libglib-2.0.so.0 + 0x54d4f)
                #9  0x00007f23be7705c8 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa95c8)
                #10 0x00007f23be71b463 g_main_loop_run (libglib-2.0.so.0 + 0x54463)
                #11 0x00005629ac78cccd main (NetworkManager + 0x51ccd)
                #12 0x00007f23be4c3560 __libc_start_call_main (libc.so.6 + 0x2d560)
                #13 0x00007f23be4c360c __libc_start_main_impl (libc.so.6 + 0x2d60c)
                #14 0x00005629ac78d27e _start (NetworkManager + 0x5227e)
                
                Stack trace of thread 209999:
                #0  0x00007f23be59b83f __GI___poll (libc.so.6 + 0x10583f)
                #1  0x00007f23be77055c g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa955c)
                #2  0x00007f23be7195d3 g_main_context_iteration (libglib-2.0.so.0 + 0x525d3)
                #3  0x00007f23be719621 glib_worker_main (libglib-2.0.so.0 + 0x52621)
                #4  0x00007f23be746d72 g_thread_proxy (libglib-2.0.so.0 + 0x7fd72)
                #5  0x00007f23be523aaf start_thread (libc.so.6 + 0x8daaf)
                #6  0x00007f23be5a8700 __clone3 (libc.so.6 + 0x112700)
                
                Stack trace of thread 210000:
                #0  0x00007f23be59b83f __GI___poll (libc.so.6 + 0x10583f)
                #1  0x00007f23be77055c g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa955c)
                #2  0x00007f23be71b463 g_main_loop_run (libglib-2.0.so.0 + 0x54463)
                #3  0x00007f23be9735ca gdbus_shared_thread_func (libgio-2.0.so.0 + 0x1115ca)
                #4  0x00007f23be746d72 g_thread_proxy (libglib-2.0.so.0 + 0x7fd72)
                #5  0x00007f23be523aaf start_thread (libc.so.6 + 0x8daaf)
                #6  0x00007f23be5a8700 __clone3 (libc.so.6 + 0x112700)
                
                Stack trace of thread 210001:
                #0  0x00007f23be5a0f7d syscall (libc.so.6 + 0x10af7d)
                #1  0x00007f23be76dc1c g_cond_wait_until (libglib-2.0.so.0 + 0xa6c1c)
                #2  0x00007f23be6ec071 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x25071)
                #3  0x00007f23be74a02a g_thread_pool_thread_proxy.lto_priv.0 (libglib-2.0.so.0 + 0x8302a)
                #4  0x00007f23be746d72 g_thread_proxy (libglib-2.0.so.0 + 0x7fd72)
                #5  0x00007f23be523aaf start_thread (libc.so.6 + 0x8daaf)
                #6  0x00007f23be5a8700 __clone3 (libc.so.6 + 0x112700)

GNU gdb (GDB) Red Hat Enterprise Linux 10.2-9.el9
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/NetworkManager...
Reading symbols from /usr/lib/debug/usr/sbin/NetworkManager-1.35.6-29614.copr.7895a9d7e2.fc34.x86_64.debug...
[New LWP 209998]
[New LWP 209999]
[New LWP 210000]
[New LWP 210001]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/NetworkManager --no-daemon'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
44	      return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0;
[Current thread is 1 (Thread 0x7f23bd4124c0 (LWP 209998))]
(gdb) #0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x00007f23be525863 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#2  0x00007f23be4d8676 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3  0x00007f23be4c27d3 in __GI_abort () at abort.c:79
#4  0x00007f23be6e5d4c in g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=<optimized out>, message=<optimized out>) at ../glib/gtestutils.c:3065
#5  0x00007f23be74698f in g_assertion_message_expr (domain=0x5629aca70359 "nm", file=0x5629aca62aab "src/core/nm-l3cfg.c", line=2395, func=0x5629acb26b30 <__func__.72.lto_priv.4> "_l3_acd_data_state_change", expr=<optimized out>) at ../glib/gtestutils.c:3091
#6  0x00005629ac937e46 in _l3_acd_data_state_change (self=0x5629add69790, acd_data=0x5629add8d520, state_change_mode=ACD_STATE_CHANGE_MODE_TIMEOUT, sender_addr=0x0, p_now_msec=0x7ffded506460) at src/core/nm-l3cfg.c:2395
#7  0x00005629ac939f4d in _l3_acd_data_timeout_cb (user_data=user_data@entry=0x5629add8d520) at src/core/nm-l3cfg.c:1933
#8  0x00007f23be71c5a1 in g_timeout_dispatch (source=0x5629addd7a80, callback=0x5629ac939ee0 <_l3_acd_data_timeout_cb>, user_data=0x5629add8d520) at ../glib/gmain.c:4889
#9  0x00007f23be71bd4f in g_main_dispatch (context=0x5629adc6da00) at ../glib/gmain.c:3337
#10 g_main_context_dispatch (context=0x5629adc6da00) at ../glib/gmain.c:4055
#11 0x00007f23be7705c8 in g_main_context_iterate.constprop.0 (context=0x5629adc6da00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4131
#12 0x00007f23be71b463 in g_main_loop_run (loop=0x5629adc4f470) at ../glib/gmain.c:4329
#13 0x00005629ac78cccd in main (argc=<optimized out>, argv=<optimized out>) at src/core/main.c:509
(gdb) quit


Version-Release number of selected component (if applicable):
1.35.6-29614.copr.7895a9d7e2.fc34

How reproducible:
not sure, the test is quite long, we've seen the crash just twice so far

Steps to Reproduce:
1. test=dhcp-timeout_infinity; a=0; while ./test_run.sh $test; do :;((a++)); echo "ATTEMPT $a"; if [ $a -eq 100 ]; then break; fi ; done

Actual results:
no crash

Expected results:


Additional info:

Comment 1 Thomas Haller 2022-02-01 16:21:54 UTC
Also: https://faf.lab.eng.brq.redhat.com/faf/reports/28232/

Comment 5 Vladimir Benes 2022-02-16 12:09:30 UTC
We seen no crashes since     2022-02-09 
-> VERIFIED

Comment 8 errata-xmlrpc 2022-05-17 15:48:19 UTC
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 (new packages: NetworkManager), 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://access.redhat.com/errata/RHBA-2022:3915


Note You need to log in before you can comment on or make changes to this bug.