Bug 2233004

Summary: NetworkManager daemon crashes when rollback a checkpoint
Product: Red Hat Enterprise Linux 9 Reporter: Gris Ge <fge>
Component: NetworkManagerAssignee: NetworkManager Development Team <nm-team>
Status: CLOSED MIGRATED QA Contact: Vladimir Benes <vbenes>
Severity: high Docs Contact:
Priority: high    
Version: 9.3CC: bgalvani, desktop-qa-list, lrintel, rkhan, sfaye, sukulkar, till
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: 9.4   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-21 12:28:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Core dump none

Description Gris Ge 2023-08-21 02:48:07 UTC
Created attachment 1984255 [details]
Core dump

Description of problem:

(gdb) bt
#0  0x000055db671a6b86 in nm_checkpoint_rollback (self=0x55db67701ce0) at src/core/nm-checkpoint.c:471
#1  0x000055db671a6ed1 in rollback_checkpoint (self=0x7f3224006080, checkpoint=0x55db67701ce0) at src/core/nm-checkpoint-manager.c:90
#2  0x000055db671a77a0 in nm_checkpoint_manager_rollback
    (error=0x7ffc0f3e8910, results=<synthetic pointer>, path=0x7f322000ea40 "/org/freedesktop/NetworkManager/Checkpoint/1", self=0x7f3224006080)
    at src/core/nm-checkpoint-manager.c:251
#3  checkpoint_auth_done_cb (chain=0x7f3220010430, context=0x55db677d1ce0, user_data=<optimized out>) at src/core/nm-manager.c:8420
#4  0x000055db67046bb4 in _done_and_destroy (self=0x7f3220010430) at src/core/nm-auth-utils.c:99
#5  pk_call_cb (auth_manager=<optimized out>, user_data=0x55db67791e40, error=0x0, is_challenge=0, is_authorized=1, call_id=<optimized out>) at src/core/nm-auth-utils.c:391
#6  pk_call_cb (auth_manager=<optimized out>, call_id=<optimized out>, is_authorized=1, is_challenge=0, error=0x0, user_data=0x55db67791e40) at src/core/nm-auth-utils.c:354
#7  0x000055db67048835 in _call_id_invoke_callback (error=0x0, is_challenge=0, is_authorized=1, call_id=0x55db67764c00) at src/core/nm-auth-manager.c:180
#8  _call_on_idle (user_data=0x55db67764c00) at src/core/nm-auth-manager.c:284
#9  0x00007f322f13c13b in g_idle_dispatch () at /lib64/libglib-2.0.so.0
#10 0x00007f322f13fe2f in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#11 0x00007f322f195108 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0
#12 0x00007f322f13f483 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#13 0x000055db66f65753 in main (argc=<optimized out>, argv=<optimized out>) at src/core/main.c:519

Version-Release number of selected component (if applicable):
NetworkManager-1.45.1-32537.copr.712729f652.el9.x86_64

How reproducible:
100%

Steps to Reproduce:

echo '---
interfaces:
  - name: dummy1
    type: dummy
  - name: dummy1.101
    type: vlan
    state: up
    vlan:
      base-iface: dummy1
      id: 101' | sudo nmstatectl set - --no-commit; sudo nmstatectl rollback

Actual results:

NetworkManager daemon crash

Expected results:

No crash

Additional info:

The checkpoint is widely used in openshift, hence high priority.

Comment 1 sfaye 2023-08-21 12:16:44 UTC
This bug has been scheduled for migration to Jira (https://issues.redhat.com).

Please, let me know if you face any problems once it is done (Jira login creation, etc.).

For guidance about your Jira account or creating one if needed, use the following KB articles: KB0016394, KB0016694, KB0016774.

Comment 2 RHEL Program Management 2023-08-21 12:22:57 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-08-21 12:28:02 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.