Bug 1379711

Summary: Restarting NetworkManager causes devices to be lost from the network connections
Product: Red Hat Enterprise Linux 7 Reporter: Marcel Kolaja <mkolaja>
Component: NetworkManagerAssignee: Lubomir Rintel <lrintel>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 7.2CC: aloughla, atragler, bgalvani, bmcclain, danken, dpathak, lkundrak, lrintel, mburman, mleitner, msugaya, ptalbert, rhepner, rkhan, snagar, sserna, sukulkar, thaller, tlavigne, vanhoof, vbenes, ylavi
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1333983 Environment:
Last Closed: 2016-10-26 16:20:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1333983    
Bug Blocks:    

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.