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.
Created attachment 1900648[details]
core dump
Description of problem:
Version-Release number of selected component (if applicable):
NetworkManager-config-server-1:1.39.10-1.el8.noarch
NetworkManager-ovs-1:1.39.10-1.el8.x86_64
glib-networking-2.56.1-1.1.el8.x86_64
How reproducible:
once
Steps to Reproduce:
1. apply desired state via nmstate.
this entails numerous calls which are listed in the attached supervdsm.log
Actual results:
Destroy checkpoint call crashes the caller (vdsm) and produces the attached core dump. See attached supervdsm.log:
```
MainProcess|jsonrpc/4::DEBUG::2022-08-01 12:27:02,829::context::148::root::(register_async) Async action: Destroy checkpoint /org/freedesktop/NetworkManager/Checkpoint/7 started
```
Expected results:
Additional info:
nmstate-1.3.1-1.el8.x86_64
Hi Thomas,
Unfortunately we only saw this once in our automatic network tests suite.
This suite runs ~24 times per day and run envs are rolled over every couple of hours or so.
So at the mo I can't provide any more info or a reproducing env, but if we come across this again I will ping you immediately.
Reproducing this manually would require running the suite, but they are constantly running anyway so monitoring the runs for this failure is the same imo because I do not see in the logs any specific action that could caused this failure.
HTH,
Eitan
Hi @eraviv,
I am closing this as insufficient data for now as it is hard to investigate it. Please feel free to reopen it if you come across this again.
Thanks
Created attachment 1900648 [details] core dump Description of problem: Version-Release number of selected component (if applicable): NetworkManager-config-server-1:1.39.10-1.el8.noarch NetworkManager-ovs-1:1.39.10-1.el8.x86_64 glib-networking-2.56.1-1.1.el8.x86_64 How reproducible: once Steps to Reproduce: 1. apply desired state via nmstate. this entails numerous calls which are listed in the attached supervdsm.log Actual results: Destroy checkpoint call crashes the caller (vdsm) and produces the attached core dump. See attached supervdsm.log: ``` MainProcess|jsonrpc/4::DEBUG::2022-08-01 12:27:02,829::context::148::root::(register_async) Async action: Destroy checkpoint /org/freedesktop/NetworkManager/Checkpoint/7 started ``` Expected results: Additional info: nmstate-1.3.1-1.el8.x86_64