Bug 14117

Summary: When ifupdown ist configured for DHCP with IPv6 the system boot hangs
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Simon <simon_i83>
Component: coreAssignee: Yi Zhao <yi.zhao>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: meta.mr.watcher, meta.watcher, randy.macleod, yi.zhao
Version: 3.0.5   
Target Milestone: 3.4 M4   
Hardware: Other   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
The patch i used to fix the problem none

Description Simon 2020-11-06 01:48:57 UTC 
Created attachment 4748 [details]
The patch i used to fix the problem

When dhclient is used with ifupdown and in the /etc/network/interfaces file is something like e.g. "iface eth0 inet6 dhcp" the system does not boot but hangs at the after dhcp configuration of IPv4 at the stage where IPv6 should be configured.

The reason seems to be, that ifupdown calls the dhclient in a blocking way which leads to a permanent block of the boot (with sysvinit) when no DHCPv6 server is available.

In the attachment you find a .bbappend and a small patch for ifupdown which calls dhclient with -1 when -6 option is used.

(A similar bug in redhat is described here: https://bugzilla.redhat.com/show_bug.cgi?id=585047)

PS: I see the problem in zeus - but it might be in any other version as well.
Comment 1 Randy MacLeod 2020-11-12 15:36:19 UTC 
Yi, Please evaluate for both master and previous releases that are supported still.
Comment 2 Yi Zhao 2020-12-23 01:26:30 UTC 
Hi Simon,

I have tested your patch and it looks good to me. But the dhcp has been removed since Gatesgarth (3.2). And the Zeus(3.0) is EOL. Currently, the dhcpc only exists on Dunfell(3.1). Would you please rebase your patch to Dunfell and send it to the mailing list with [dunfell] tag?