Bug 8391

Summary: can't create /var/lib/dhclient/dhclient--eth0.lease: No such file or directory
Product: Mageia Reporter: Dave Hodgins <davidwhodgins>
Component: RPM PackagesAssignee: Guillaume Rousse <guillomovitch>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: oe
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: 3beta2
Source RPM: dhcp-4.2.4P2-1.mga3.src.rpm CVE:
Status comment:

Description Dave Hodgins 2012-12-15 03:03:06 CET
After installing kde from the beta1 pre-release iso, journalctl shows
dhclient[940]: can't create /var/lib/dhclient/dhclient--eth0.lease: No such file or directory
Dave Hodgins 2012-12-15 03:03:20 CET

Whiteboard: (none) => 3beta1

Dave Hodgins 2012-12-15 22:54:53 CET

CC: (none) => oe
Assignee: bugsquad => guillomovitch

Comment 1 Guillaume Rousse 2012-12-18 19:41:44 CET
Strange issue, as both the client and the server were supposed to use /var/lib/dhcp as state directory, shipped in dhcp-common package.

Anyway, I just submited 4.2.4P2-2.mga3, with the client using /var/lib/dhclient as state directory, as on fedora. This should fix this issue.
Comment 2 Dave Hodgins 2013-01-22 21:20:12 CET
With Mageia 3 beta 2 3rd build of the pre-release iso images, the message is

Jan 21 21:02:46 localhost dhclient[1857]: can't create /var/lib/dhcp/dhclient-5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03-eth0.lease: No such file or directory

This is with the gnome live cd.  dhcp-common-4.2.4P2-4.mga3 is installed,
but only has the doc and man files.

Whiteboard: 3beta1 => 3beta2

Comment 3 Guillaume Rousse 2013-02-06 20:19:44 CET
Reproduced here. Something external to dhcp-client package configuration seems to enforce usage of a non-default lease directory, and I can't find what exactly...
Comment 4 Guillaume Rousse 2013-02-06 23:15:38 CET
According to get_dhclient_leasefile function in nm-dhcp-dhclient.c code, NetworkManager should uses its own NMSTATEDIRstate directory to store dhclient leases files. However, this is clearly not the case, as the filename pattern is clearly the one used in this function...

Status: NEW => ASSIGNED

Comment 5 Guillaume Rousse 2013-03-02 15:31:19 CET
Fixed with the switch to network manager 0.9.8.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED