Bug 1915278 - null error when deleting veth device
Summary: null error when deleting veth device
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Fernando F. Mancera
QA Contact: Vladimir Benes
Depends On:
TreeView+ depends on / blocked
Reported: 2021-01-12 11:35 UTC by Vladimir Benes
Modified: 2021-11-10 06:47 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.32.0-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-11-09 19:28:55 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4361 0 None None None 2021-11-09 19:29:34 UTC

Description Vladimir Benes 2021-01-12 11:35:54 UTC
Description of problem:

nmcli con del test11+ test12+
nmcli  connection add type veth con-name test11+ ifname test11 veth.peer test12 ip4
nmcli  connection add type veth con-name test12+ ifname test12 veth.peer test11 ip4
nmcli con up test12+
while ! nmcli -g GENERAL.STATE con show test11+ |grep activated; do :;sleep 1;done 
nmcli dev del test11

Error: Device '(null)' (/org/freedesktop/NetworkManager/Devices/16) deletion failed: Message recipient disconnected from message bus without replying
Error: not all devices deleted.

deleting a device should bring all affected connections down being it veth.peer or veth device directly.

Version-Release number of selected component (if applicable):

Comment 1 Vladimir Benes 2021-06-15 14:05:26 UTC
NMCI test case added:

Comment 8 errata-xmlrpc 2021-11-09 19:28:55 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 (Moderate: NetworkManager security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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