Bug 1448165 - NetworkManager does not track ip configurations on managed, inactive devices
Summary: NetworkManager does not track ip configurations on managed, inactive devices
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Francesco Giudici
QA Contact: Desktop QE
Depends On:
TreeView+ depends on / blocked
Reported: 2017-05-04 16:28 UTC by Francesco Giudici
Modified: 2017-08-01 09:28 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.8.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-01 09:28:57 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2299 normal SHIPPED_LIVE Moderate: NetworkManager and libnl3 security, bug fix and enhancement update 2017-08-01 12:40:28 UTC

Description Francesco Giudici 2017-05-04 16:28:55 UTC
Description of problem:
When an ip configuration is added with a tool external to NetworkManager (e.g., the ip tool) to a device inactive but managed by NetworkManager, NetworkManager does not create anymore a tracking connection nor is able to assume the connection.

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

How reproducible:
add a static ip configuration to a managed and not active device: no connection is created/activated by NetworkManager

Steps to Reproduce:
1. ip add add dev eth1
2. ip add show eth1
3. nmcli conn show

Actual results:
ip configuration is there and shown with "ip add show" but no tracking connection from NetworkManager is created

Expected results:
NetworkManager creates/activates a connection to track the newly got ip address

Additional info:

Comment 4 errata-xmlrpc 2017-08-01 09:28:57 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, 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.