Bug 1379711 - Restarting NetworkManager causes devices to be lost from the network connections
Summary: Restarting NetworkManager causes devices to be lost from the network connections
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.2
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Lubomir Rintel
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1333983
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-27 13:38 UTC by Marcel Kolaja
Modified: 2019-12-16 06:54 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1333983
Environment:
Last Closed: 2016-10-26 16:20:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Marcel Kolaja 2016-09-27 13:38:11 UTC 
This bug has been copied from bug #1333983 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 3 Lubomir Rintel 2016-09-27 13:59:17 UTC 
Following up to requests to fix this in 7.2.

As has been discussed previously (bug #1333983 comment #21), this is non-trivial and somewhat risky to backport to the 7.2 code base :(

Bronce, Yuri, I'd be very thankful if you could help me the use case, in particular the reason behind restarting NetworkManager. That way we could perhaps find an alternative solution/workaround.
Comment 4 Yaniv Lavi 2016-09-27 15:23:11 UTC 
(In reply to Lubomir Rintel from comment #3)
> Following up to requests to fix this in 7.2.
> 
> As has been discussed previously (bug #1333983 comment #21), this is
> non-trivial and somewhat risky to backport to the 7.2 code base :(
> 
> Bronce, Yuri, I'd be very thankful if you could help me the use case, in
> particular the reason behind restarting NetworkManager. That way we could
> perhaps find an alternative solution/workaround.

We use Cockpit to create basic networking on the host and then switch to use out host agent for day 2. The networking dies due to this issue. This is very severe.
Comment 5 Lubomir Rintel 2016-10-25 15:16:07 UTC 
(In reply to Yaniv Dary from comment #4)
> (In reply to Lubomir Rintel from comment #3)
> > Following up to requests to fix this in 7.2.
> > 
> > As has been discussed previously (bug #1333983 comment #21), this is
> > non-trivial and somewhat risky to backport to the 7.2 code base :(
> > 
> > Bronce, Yuri, I'd be very thankful if you could help me the use case, in
> > particular the reason behind restarting NetworkManager. That way we could
> > perhaps find an alternative solution/workaround.
> 
> We use Cockpit to create basic networking on the host and then switch to use
> out host agent for day 2. The networking dies due to this issue. This is
> very severe.

Note that this is probably a different issue. The original bug report dealt with NetworkManager not being able to pick up a device on start when it lacked L3 configuration. The issue you're experiencing seems to be in the shutdown path.

I think the actual bug you're experiencing is tracked in bug #1371126
Comment 6 Lubomir Rintel 2016-10-26 16:20:09 UTC 
Fixed in 7.3, not feasible for 7.2.
Note You need to log in before you can comment on or make changes to this bug.