Bug 1193988

Summary:	No IP address acquired by dhclient
Product:	[Fedora] Fedora	Reporter:	Thomas Schweikle <tschweikle>
Component:	dhcp	Assignee:	Jiri Popelka <jpopelka>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	jpopelka, thozza
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-19 15:04:15 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:
Embargoed:

Description Thomas Schweikle 2015-02-18 17:03:31 UTC

Description of problem:
Installed Version of dhclient (dhcp-client-4.3.2-0.2b1) does not aquire IP address.

Version-Release number of selected component (if applicable):
dhcp-client-4.3.2-0.2b1

How reproducible:
always

Steps to Reproduce:
1. Install Fedora 21, Upgrade to Fedora 22 or 23
2. No IP-address acquired by dhclient
3.

Actual results:
No IP address acquired by dhclient started in background. ps reports it running:

dhclient -H f22-64 -1 -q -lf /var/lib/dhclient/dhclient--ens33.lease -pf /var/run/dhclient-ens33.pid

Expected results:
Acquire IP address, register system with DNS

Additional info:

Comment 1 Thomas Schweikle 2015-02-18 17:03:58 UTC

Same for Fedora 23.

Comment 2 Thomas Schweikle 2015-02-18 17:06:31 UTC

Starting dhclient manually with the same options, but removing "-1" makes it work as expected.

Comment 3 Jiri Popelka 2015-02-18 17:22:14 UTC

If that's possible could you try to downgrade back to dhcp-4.3.1 ?
https://koji.fedoraproject.org/koji/buildinfo?buildID=608858
I just want to know whether this is related to 4.3.1 -> 4.3.2 update.

If you can see the same with 4.3.1, then is probably bug #1193944 related.

Comment 4 Thomas Schweikle 2015-02-19 13:17:08 UTC

Yes it is related to #1193944. And to #1184173, #1154200.
Maybe it is related to #1154200 and #1177484 too.

I've tried:
dhclient not running in background -> not loosing address
dhclient not given option -lf -> not loosing address

Comment 5 Jiri Popelka 2015-02-19 15:04:15 UTC

(In reply to Thomas Schweikle from comment #4)
> Yes it is related to #1193944. And to #1184173
>
> dhclient not running in background -> not loosing address

Thanks, closing as duplicate of bug #1184173 then.

*** This bug has been marked as a duplicate of bug 1184173 ***