Bug 1332690

Summary:	Loosing SIGCHLD notifications
Product:	[Fedora] Fedora	Reporter:	Marcelo Ricardo Leitner <mleitner>
Component:	NetworkManager	Assignee:	Lubomir Rintel <lkundrak>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	23	CC:	dcbw, fgiudici, lkundrak, psimerda
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-20 20:16:59 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:

Description Marcelo Ricardo Leitner 2016-05-03 19:21:26 UTC

Description of problem:
long story short:
If I kill dhclient process, it may not come back:
root      2122  0.2  0.0 522904 13064 ?        Ssl  16:07   0:00 /usr/sbin/Netwo
rkManager --no-daemon
root      2486  0.0  0.0      0     0 ?        Z    16:07   0:00  \_ [dhclient] <defunct>

long story with the glory details:
I have a bridge which takes its address using dhcp. That bridge is also used by guests to access my LAN segment. Time to time the bridge starts with the wrong MAC address (vnet0 one) and then I just kill dhclient so it tries again. That's when it sometimes gets stuck in that situation with dhclient as zombie. Then I have to restart NetworkManager too.

Version-Release number of selected component (if applicable):
NetworkManager-1.0.12-2.fc23.x86_64

How reproducible:
Not always, but quite often.

Steps to Reproduce:
1.setup an interface to use dhcp
2.bring it up
3.kill dhclient
4.check if it became a zombie

Actual results:
Sometimes dhclient process is not cleaned and doesn't come back

Expected results:
dhclient to be fully restarted, as it was a kill but it could have been an app crash and it should keep working

Additional info:

Comment 1 Fedora End Of Life 2016-11-25 08:55:56 UTC

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2016-12-20 20:16:59 UTC

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.